Skip to content

fix: sort YAML config files by name for deterministic schema order#1244

Open
benji07 wants to merge 1 commit intooverblog:masterfrom
benji07:fix/sort-config-files-by-name
Open

fix: sort YAML config files by name for deterministic schema order#1244
benji07 wants to merge 1 commit intooverblog:masterfrom
benji07:fix/sort-config-files-by-name

Conversation

@benji07
Copy link
Copy Markdown
Contributor

@benji07 benji07 commented Apr 23, 2026

Q A
Bug fix? yes
New feature? no
BC breaks? no
Deprecations? no
Tests pass? yes
Documented? no
License MIT

ConfigParserPass::detectFilesByTypes() uses Symfony\Finder without sorting, so the discovery order of YAML/GraphQL config files follows the underlying filesystem's readdir order.

This order differs between filesystems — notably between APFS (macOS) accessed via VirtioFS in Docker Desktop, and ext4 on a Linux CI runner. The resulting schemas are functionally identical but contain fields and types declared in a different order.

Impact

Teams running a git diff --exit-code schema.graphql check in CI see false positives: a developer regenerates the schema locally on macOS, commits it, and CI fails on Linux with a large reorder-only diff — even though no source change was made.

Fix

Add ->sortByName() to the Finder so file discovery is alphabetical, stable, and platform-independent.

Symfony Finder returns files in filesystem readdir order, which differs
between filesystems (APFS/VirtioFS on macOS Docker Desktop vs ext4 on a
Linux CI runner). Running graphql:dump-schema on two different platforms
can therefore produce two valid schemas that only differ in the order of
fields and type declarations, which breaks 'git diff --exit-code' checks
on schema.graphql even when no source change was made.

Add ->sortByName() so the discovery order is stable and platform-independent.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant