Skip to content

Comments

perf(linter): refactor react/only-export-components to use enum matching#14702

Closed
camchenry wants to merge 1 commit into10-16-perf_linter_remove_simple_phf_map_callsfrom
10-16-perf_linter_refactor_react_only-export-components_to_use_enum_matching
Closed

perf(linter): refactor react/only-export-components to use enum matching#14702
camchenry wants to merge 1 commit into10-16-perf_linter_remove_simple_phf_map_callsfrom
10-16-perf_linter_refactor_react_only-export-components_to_use_enum_matching

Conversation

@camchenry
Copy link
Member

No description provided.

@github-actions github-actions bot added A-linter Area - Linter C-performance Category - Solution not expected to change functional behavior, only performance labels Oct 17, 2025
Copy link
Member Author

camchenry commented Oct 17, 2025

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more


How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

  • 0-merge - adds this PR to the back of the merge queue
  • hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

@codspeed-hq
Copy link

codspeed-hq bot commented Oct 17, 2025

CodSpeed Performance Report

Merging #14702 will not alter performance

Comparing 10-16-perf_linter_refactor_react_only-export-components_to_use_enum_matching (aa42dff) with 10-16-perf_linter_remove_simple_phf_map_calls (b42a79f)1

Summary

✅ 4 untouched
⏩ 33 skipped2

Footnotes

  1. No successful run was found on 10-16-perf_linter_remove_simple_phf_map_calls (b42a79f) during the generation of this report, so 995955a was used instead as the comparison base. There might be some changes unrelated to this pull request in this report.

  2. 33 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports.

@camc314 camc314 self-assigned this Oct 17, 2025
@camchenry camchenry force-pushed the 10-16-perf_linter_remove_simple_phf_map_calls branch from a55ef9e to b42a79f Compare October 18, 2025 23:16
@camchenry camchenry force-pushed the 10-16-perf_linter_refactor_react_only-export-components_to_use_enum_matching branch from 6746f48 to aa42dff Compare October 18, 2025 23:16
@camchenry camchenry closed this Oct 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-linter Area - Linter C-performance Category - Solution not expected to change functional behavior, only performance

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants