Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Applyfilterasync - enhancement #278

Open
jstrauss18 opened this issue Oct 21, 2019 · 1 comment
Open

Applyfilterasync - enhancement #278

jstrauss18 opened this issue Oct 21, 2019 · 1 comment

Comments

@jstrauss18
Copy link

This method is most excellent for dynamically updating filters. However, the problem we run into is when users deploy custom saved views, then the filters saved by the user should take precedence.

Within the extension logic, we can inspect the "document.url" and make a determination of a custom saved view by existence of the @ sign. And this works well. The time that this doesn't work is when we are embedding a view and the user chooses to set the custom saved view as default. At this point, we never see the @ sign in the URL.

@Kovner
Copy link
Contributor

Kovner commented Jan 2, 2020

Hi Jeff,
We have some upcoming work related to handling Custom Views in the Extensions API a little bit better. Your request makes complete sense and we will incorporate it when we start the work to improve Custom Views support. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants