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
Currently, Link can be assigned query args only as strings using search param. It would be better to extend it to accept objects, which are serialized by the router.
For active Routes, the query args. are only accessible as strings. It would be better to make them accessible as object.
While using Google Analytics (GA) or any analytics engine, we do not want to record personally identifiable info. in GA, like /user/.
GA provides a way to pre-process URLs using regex, before being recorded. However, if only path params are used, configuring the filter regex becomes tedious, but it is much easier to simply filter out query args. In such cases one would prefer to use query args instead of path args to design there routes.
Serializing/Deserializing Query Strings
Currently,
Link
can be assigned query args only as strings usingsearch
param. It would be better to extend it to accept objects, which are serialized by the router.For active Routes, the query args. are only accessible as strings. It would be better to make them accessible as object.
The above was supported in old version at Query Param Example.
Use Case
While using Google Analytics (GA) or any analytics engine, we do not want to record personally identifiable info. in GA, like /user/.
GA provides a way to pre-process URLs using regex, before being recorded. However, if only path params are used, configuring the filter regex becomes tedious, but it is much easier to simply filter out query args. In such cases one would prefer to use query args instead of path args to design there routes.
Examples
The text was updated successfully, but these errors were encountered: