Ability to opt-out of certain parameters tracked in URL state
See original GitHub issueThe use case is something like this:
As a developer, I want to hardcode certain parameters and thus would not like them to be exposed in the URL.
From an implementation perspective, it IS possible to hardcode parameters by configuring them in the searchQuery
option.
Example:
<SearchProvider
config={{
apiConnector: connector,
searchQuery: {
resultsPerPage: 6
},
}}
>
This hardcodes the value to 6, so it is always sent as 6 on API requests.
However, “size” (the corresponding URL parameter) is still exposed in the query string, though it is no longer functional.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Implement opt-out links - Analytics - Adobe Experience League
Single click opt-out Allows the user to immediately opt out of tracking. Add the two query string parameters opt_out and confirm_change , giving...
Read more >The Ultimate Guide to Compliant Tracking: Google Analytics 4
These are parameters that are scoped to (associated with) the user being tracked. Some standard User Properties are always collected within GA4 ...
Read more >Consent mode on websites and mobile apps - Analytics Help
Consent mode lets you communicate your users' cookie or app identifier consent status to Google. Tags adjust their behavior and respect users' choices....
Read more >Opt In vs Opt Out: What's the Difference? | Termly
Consent withdrawal is when you offer users a way to withdraw their permission or change their preferences after the original point of consent....
Read more >Opt-in Vs Opt-out: What they are and How to Implement Each
Let us look at the difference between opt-in and opt-out and the scenarios where you should use them and how to implement each...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@m-sureshraj This issue might actually be a little tricky. I’m unsure of exactly how this should work at this point, so it will require a bit of thought. You’re welcome to play around with it and submit a PR as a proposal.
However, I also marked some other issues with the “Good first issue” tag. These are issues isolated to specific components, which I think is a good place to start with Search UI. https://github.com/elastic/search-ui/labels/good first issue
This one, in particular I think would be a great first issue: https://github.com/elastic/search-ui/issues/60.
There is a contributor guide here to help get you set up and started: https://github.com/elastic/search-ui/blob/master/ADVANCED.md#search-ui-contributors-guide.
There is a gitter set up for chat about the project: https://gitter.im/elastic-search-ui/community. Feel free to post there if you need help.
Tracking work related to this issue here: https://github.com/elastic/search-ui/issues/790