ref(AccountSecurityEnroll): Re-order methods to make diffs readable #95405
+54
−54
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
the
Scope: Frontend
Codecov ReportAll modified and coverable lines are covered by tests ✅ ✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## master #95405 +/- ##
==========================================
- Coverage 87.84% 87.80% -0.05%
==========================================
Files 10502 10495 -7
Lines 608126 606000 -2126
Branches 23719 23715 -4
==========================================
- Hits 534228 532070 -2158
- Misses 73540 73572 +32
Partials 358 358 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Just moving two functions from lower in the file, up higher in the file.
All the other callbacks depend on these two callbacks, so when we move to a functional component these will need to be defined at the top. Therefore, this PR will make the next set one slightly easier to read.
Related to https://github.com/getsentry/frontend-tsc/issues/2