Queries in sidebar

[denisahearn]

What?

Moves the queries out to a separate Queries section in the sidebar, and gives each query its own page, just like mutations.

Why?

Having all the queries listed on a single page makes it difficult to read the documentation, especially when you customize the generation of the documentation, like my company has done, to embed one or more examples per query into the operation/query/index.html page.

Putting each query on a separate page and then providing navigation to these pages via a new Queries section in the sidebar makes it much easier to see what queries exist and to read this documentation (and in our case to access and run the query examples in GraphiQL).

Before

After (two screenshots, one of the Query page, and the other of the codeOfConduct query page)

[brettchalupa]

@denisahearn thank you so much for this contribution! The code looks good at first review. I'm going to do some testing locally first on your branch. 👍

[brettchalupa]

I tested this locally, and it's working well. The test failures are due to a Dart Sass deprecation warning. I'll go ahead and fix that and then merge this in. 👍 Thanks again!

With the sidebar content getting longer, it has me thinking that foldable sections and a simple search to filter could be helpful. 🤔

[denisahearn]

@brettchalupa Thanks so much for accepting my submission and for releasing a new version of the gem so quickly!

I agree that the sidebar could use some enhancing. I can't promise anything, but as time allows I'll try to look at making the sections expandable/collapsible, and the sidebar searchable using plain vanilla JavaScript.