In the entry point, mirror undefined (but valid) query parameters on every resource type collection link

For some reason I don't have next and previous on my json on any entity (!?), but I'd say all.

On the root `/jsonapi` I would need the query string on every sub entity type, so that gatsby can properly follow all links with the same query string, so it seems it's not just `_self`.

Adding organization

What is the rationale behind this? What does this query parameter convey? Because for example a ?filter query parameter's value usually only makes sense for a particular resource type (e.g. node--article), not for all resource types.

My use case is a typical (mostly) microsite approach. The driver for each microsite is a taxonomy term that is present exclusively on the content types. A goal for this project was to keep the drupal part as easy as possible, both in terms of admin and in terms of maintainability/development. Less fields, less entities nesting, less complex options in favor of more concrete and flexible coding approaches. So I have content types that have paragraphs that have other related entities as medias. Also I wanted to avoid mulit-site if at all possible. Entity access, although still an option, I still think, IMO, that adds unnecessary complexity.

I use this for Gatsby, so Gatsby needs to pulls the content for each microsite. So far I have been pulling everything and doing the filtering on gatsby's graphql side, which is OK, but to take advantage of some design decisions on gatsby and to prevent each microsite taking a lot to build once there's enough content in there I rather just make sure that jsonapi only outputs what the microsite needs.

So my rationale is to give gatsby the follwing URL for the jsonapi backend:

https://www.example.com/jsonapi?micro_site=TID

I am already successfully altering the queries to properly filter what I need with hook_query_TAG_alter() as mentioned on #3023444: Add a query tag to the entity query for other modules to perform alterations, but gatsby crawls all subsequent entities without this query string, as it follows what comes out of the initial `/jsonapi`.

I hope this helps.

I have a workaround in place with an interceptor on the gatsby request that appends this query string to every URL, I just `expected` that the querystring would be there.

And just to note something on the titile, I wonder if it's just the entry point, and not every single URL generated on the `_links` section of every endpoint.