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

in CFN documentation, make filter view (YAML vs JSON) a "sticky" preference #134

Open
rhbecker opened this issue Aug 4, 2023 · 0 comments

Comments

@rhbecker
Copy link

rhbecker commented Aug 4, 2023

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Tell us about your request

I appreciate that the CFN documentation allows users to filter views to display only YAML, only JSON, or both. I would prefer that my preference be remembered, so I don't have to set it on every page view, including when I ...

  • first arrive on a CFN documentation page
  • refresh a CFN documentation page
  • click a link to go from one CFN documentation page to another
  • navigate backward and forward among CFN documentation pages

Tell us about the problem you are trying to solve. What are you trying to do, and why is it hard?

I would like to avoid needing to re-establishing my view preference on every new page view.

Are you currently working around this issue?

Yes, I select YAML from the Filter View dropdown roughly one billion times per day 😉.

What is the expected behavior with this new feature

The documentation site remembers what I most recently selected, or perhaps pulls that info from Preferences (i.e. in the same spot where themes are set to Light or Dark).

Additional context

This isn't a language issue, per se. But it also doesn't seem to fit in the coverage repo. I wasn't sure where you'd prefer it, so I'm starting here, and hoping you can relocate as you see fit.

Attachments

sticky

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

No branches or pull requests

1 participant