`firebase dataconnect:sdk:generate` generates SDK files in a non-deterministic order

[Amaimaya]

[REQUIRED] Environment info

firebase-tools:

15.11.0

Platform:

macOS

[REQUIRED] Test case

A TypeScript repository using Firebase Data Connect with generated SDK files committed to source control.

[REQUIRED] Steps to reproduce

1. Run firebase dataconnect:sdk:generate.
2. Run the command again without making any changes to the Data Connect schema, operations, or configuration.
3. Compare the generated files between runs.

[REQUIRED] Expected behavior

The output of firebase dataconnect:sdk:generate should be deterministic. Running the command multiple times without modifying any Data Connect files should produce identical SDK files and no source control diffs.

[REQUIRED] Actual behavior

The generated SDK files change every time the command is executed, even when there have been no changes to the Data Connect schema, operations, or configuration.

The differences appear to be caused by inconsistent ordering in the generated output rather than actual changes to the generated API surface. This results in unnecessary diffs being introduced into source control and makes it difficult to distinguish real changes from generation noise.

[aalej]

Thanks for reporting this @Amaimaya! It took me a couple of tries, but it does look like the generated SDK file of firebase dataconnect:sdk:generate will sometimes have a different output. From what I can tell, it changes the ordering of some methods, but still contains the same methods. Though I do agree with you, the output should be consistent.

I'll raise this with our engineering team and mark this as reproducible. Sharing my mcve - https://github.com/aalej/issues-10626

[grbaczek]

When can we expect it to be fixed? The issue is very irritating. It results in "diff noise" especially when there is multiple connectors in the same repo

[aalej]

We completely understand your situation here, unwanted "diff noise" can be irritating to deal with especially if there are no actual changes to the output(only the ordering).

I can't provide and ETA for the fix at the moment, but our engineers are taking a look into this. I can follow up with them and I'll share and update here.

[grbaczek]

cool, thank you for a quick response!

[aalej]

Quick update here: The fix for this should be available on the next Firebase CLI release, which is scheduled for this coming Wednesday