Naming the URL observable

[matthewp]

can-route 4.2.0 will introduce a new way to set what type of URL observable will be used. As the default, it is can-route-hash, but can-route-pushstate users will need to set it.

This is similar to how you set route.data to be your ViewModel. The flow will be something like:

import { route, RoutePushstate } from "can";
import AppViewModel from "./app";

route.urlData = new RoutePushstate();
route.data = new AppViewModel();

route.register("{page}");
route.start();

What is a good name for this property? Is urlData ok or something else?

cc @phillipskevin @chasenlehara @justinbmeyer

[justinbmeyer]

@matthewp How would we handle development.html? I think mapping can-route-pushstate to can-route-hash should still work.

[phillipskevin]

So the can-bind stuff is done internally? Instead of making people type something like this:

import { route, RoutePushstate, Bind } from "can";
import AppViewModel from "./app";

var routeBinding = new Bind({
    child: new AppViewModel(),
    parent: new RoutePushstate()
});

route.register("{page}");
routeBinding.start();

[phillipskevin]

I guess this would be prohibitive since there's a lot more to the binding (

can-route/can-route.js

Line 230 in b5faeb4

canRoute._canBinding = new Bind(bindingOptions);

).

[matthewp]

@phillipskevin We want to move towards more directly using can-bind in a way that users could do the same themselves if needed. So removing the internal stuff like that is something we can do in the future. This particular change is a bridge between the old API (removing backwards compatible, except for can-route-pushstate), and the new one that will work more like that, hopefully.

[matthewp]

I guess we're going to stick with urlData for now.