Skip to content

fix(typegen): use javascript deterministic sort for args join #930

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Merged
merged 1 commit into from
Apr 10, 2025

Conversation

avallete
Copy link
Member

@avallete avallete commented Apr 9, 2025

What kind of change does this PR introduce?

Should resolve: #929

@avallete avallete requested review from a team as code owners April 9, 2025 17:27
@coveralls
Copy link

Pull Request Test Coverage Report for Build 14363335713

Details

  • 1 of 1 (100.0%) changed or added relevant line in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.003%) to 75.867%

Totals Coverage Status
Change from base Build 14362646702: 0.003%
Covered Lines: 4985
Relevant Lines: 6487

💛 - Coveralls

@@ -296,6 +296,7 @@ export type Database = {
})
return `{ ${argsNameAndType.map(({ name, type, has_default }) => `${JSON.stringify(name)}${has_default ? '?' : ''}: ${type}`)} }`
})
.toSorted()
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TIL .toSorted() 🔥

@avallete avallete merged commit 0a55d33 into master Apr 10, 2025
5 checks passed
@avallete avallete deleted the fix/typescrypt-gen-args-sorting branch April 10, 2025 21:45
avallete added a commit that referenced this pull request May 13, 2025
fix(typegen): use javascript deterministic sort for args join
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Type Generation not consistent on platforms
3 participants