Where Query documentation improvements

[gsartori]

No description provided.

[bito-code-review]

This question isn’t related to the pull request. I can only help with questions about the PR’s code or comments.

[jdaugherty]

@gsartori is this ready to review again?

[gsartori]

@gsartori is this ready to review again?

Nope, ill complete it tomorrow in consideration of your review, ill comment here once done

[gsartori]

@jdaugherty I've reintroduced the paragraph about the auto-generated aliases. The PR can be reviewd 👍

[jamesfredley]

Reviewed the documentation changes against the codebase. The technical claims are accurate (delete() failOnError omission, Map-based multi-field sort, nested criteria block, properties = [...] binding, list() pagination params - all verified against DetachedCriteria.groovy, DynamicFinder.java, GormInstanceApi.groovy, DetachedCriteriaTransformer.java, and WebDataBinding). Leaving line-level suggestions for editorial / consistency / flow polish. The Map-sort feature was previously undocumented, so this PR genuinely fills a gap.

Non-blocking but worth noting:

• The PR body is empty - CONTRIBUTING.md expects a description and (where applicable) issue references.
• Branch 7.0.x -> 7.0.x skips the docs/ prefix convention from AGENTS.md, so auto-labelers won't tag this as documentation.
• The newly-documented Map-sort path (DynamicFinder.applySortForMap) has no test coverage in DetachedCriteriaSpec. Per AGENTS.md rule #10 ("every code change must include new or enhanced tests"), consider adding a small spec to lock in the contract being documented.
• grails-data-graphql/.../DeleteEntityDataFetcher.groovy incorrectly passes failOnError: true to delete() - that parameter is silently ignored. Worth filing separately.