You can put this in your own code for your own use, but this makes too many breaking changes. If you want custom URL encoding, the option already exists in route->url and url->route option of the html5 history constructor. No further changes to this ns will be accepted unless they are fixing a bug, or adding new capabilities that a non-breaking in nature.
You can put this in your own code for your own use, but this makes too many breaking changes. If you want custom URL encoding, the option already exists in
route->urlandurl->routeoption of the html5 history constructor. No further changes to this ns will be accepted unless they are fixing a bug, or adding new capabilities that a non-breaking in nature.