Skip to content

fix(discover): Avoid sorting field option inputs in place - #120724

Draft
scttcper wants to merge 2 commits into
masterfrom
scttcper/mutation/discover-field-options
Draft

fix(discover): Avoid sorting field option inputs in place#120724
scttcper wants to merge 2 commits into
masterfrom
scttcper/mutation/discover-field-options

Conversation

@scttcper

@scttcper scttcper commented Jul 28, 2026

Copy link
Copy Markdown
Member

generateFieldOptions sorted four arrays owned by its callers.

Use copied sorting for each input and mark the arrays readonly so the ownership contract is enforced by the types.

generateFieldOptions sorted four arrays owned by its callers. Use copied sorting for each input and add coverage that their order stays untouched.

Co-Authored-By: Codex <noreply@openai.com>
@github-actions github-actions Bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Jul 28, 2026
Make the ownership contract explicit in the function signature instead of relying on a regression test.

Co-Authored-By: Codex <noreply@openai.com>
@github-actions

Copy link
Copy Markdown
Contributor

📊 Type Coverage Diff

Metric Before After Delta
Coverage 94.03% 94.03% ±0%
Typed 136,673 136,672 🔴 -1
Untyped 8,670 8,671 🔴 +1
🔍 1 new type safety issue introduced

any-typed symbols (1 new)

File Line Detail
static/app/views/discover/utils.tsx 572 breakdownField (param)

This is informational only and does not block the PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant