Split queries and mutations big table

[fmontorsi-equinix]

Hi,
Today graphql-markdown is producing a single big (HTML) table listing all the possible Queries together.
A similar table is created for all available Mutations.
This means that in the TOC you have only 2 links "Queries" and "Mutations" and you cannot jump straight to a particular query or mutation... you need to scroll these tables.

In case the GraphQL schema gets large, these tables become cumbersome to navigate.
Would that be possible to produce markdown that results in each Query and each Mutation having its own Markdown subsection (just like it happens for "Objects", "Enums", etc etc) ?

I might try to submit a PR if that would be welcome

[exogen]

That sounds nice to me. I think the first iteration of this could be a smaller change, similar to #84 (see my comment there), that makes fields linkable (fine with me if we only do it for Queries, Mutations, & Subscriptions), and adds them to the TOC; that would satisfy the immediate need.

In the future it might be nice to also break them out of the single table and give them each their own sub-heading as you suggest, like so:

---

Query

lookup (LookupQuery)

Field description here.

Argument	Type	Description
...	...	...

(or maybe we could keep the table the same, with the Field / Argument columns, but only have the Field for this particular query)

browse (BrowseQuery)

...

---

That particular format could be enabled by a new CLI arg, like --query-format=section, where the default would be --query-format=table.