Make the fragment matcher deterministic

[tgandrews]

Description

This exposes a new plugin option deterministic that when enabled will ensure that the fragment matcher will always return the same result for the same schema, no matter the order it is in the schema.

It does this by sorting the results so that they are always in the same order.

The default is false to maintain backwards compatibility.

Related # (issue)

• Make the result of fragment-matcher deterministic #7367

Type of change

• New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Ran this against a small private schema and one large private schema.

• Test output is sorted without making schema changes
• Tested output remains the same after multiple schema re-ordering edits

Test Environment:

• OS: MacOS Sequoia 15.1.1
• @graphql-codegen/core: 4.0.2
• @graphql-codegen/fragment-matcher: This PR
• NodeJS: v20.18.0

Checklist:

• I have followed the CONTRIBUTING doc and the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[changeset-bot]

🦋 Changeset detected

Latest commit: 55ffbe0

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@graphql-codegen/fragment-matcher	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR