You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As suggested in #523 we should create a mechanism to share implementations of url generation. Now there are two implementations of the route parsers, and although the server-side one is abstracted by RouteBase, if someone would try to implement custom routing syntax it would fail on the client-side. It may consists of translating UrlBuilders to javascript dynamically or sharing same regex which generates url.
I think creating the UrlBuilders as Linq.Expressions would allow us to use them on server and to translate them to JS using the JavascriptTranslator we use for bindings. Parsing of the routes on client-side is not needed (yet...).
The text was updated successfully, but these errors were encountered:
As suggested in #523 we should create a mechanism to share implementations of url generation. Now there are two implementations of the route parsers, and although the server-side one is abstracted by
RouteBase
, if someone would try to implement custom routing syntax it would fail on the client-side. It may consists of translatingUrlBuilders
to javascript dynamically or sharing same regex which generates url.I think creating the UrlBuilders as
Linq.Expressions
would allow us to use them on server and to translate them to JS using the JavascriptTranslator we use for bindings. Parsing of the routes on client-side is not needed (yet...).The text was updated successfully, but these errors were encountered: