This repository has been archived by the owner on Mar 28, 2023. It is now read-only.
flow service: add support for query-strings in URLs #372
Labels
Comments
This was referenced Oct 12, 2016
x1B
added a commit
that referenced
this issue
Oct 12, 2016
x1B
added a commit
that referenced
this issue
Oct 12, 2016
Upgrade InformationThis change introduces deprecations, see below for details. Place-parameters may now be represented in URLs as query-parameters in addition to the existing representation as path segments. This allows working with places that use multiple optional place parameters, without producing URLs that contain visible placeholders (e.g. instead of To use query-parameters in URLs, the LaxarJS configuration option flow.query.enabled must be set to The following is true if query-parameters are enabled:
DEPRECATION INFORMATIONThe following methods of the
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We'd like to be able to have optional routing arguments in the form of query parameters (?key=value&...). These should be converted transparently to/from payload data for navigation events (as long as the corresponding arguments are not formally declared for path segment matching).
The text was updated successfully, but these errors were encountered: