-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Refactor][Misc] Cleaned up critical capture code. #663
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
chained ternaries are a crime
Co-authored-by: NightKev <34855794+DayKev@users.noreply.github.com>
8f9599e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm assuming the change of one threshold from 100 to 40 was intended?
If yes that also becomes a balance PR and i'd like to know why/where this was decided and have that information added in the PR description please
What are the changes the user will see?
None.
Why am I making these changes?
With this codebase, there's moments where you open a random file and see a stupid, chunky ternary.
What are the changes from a developer perspective?
Ternary broken up into if-else statements for better readability.
How to test the changes?
Critical Captures should work as expected.
Checklist
beta
as my base branchnpm run test:silent
)npm run create-test
) or updated existing tests related to the PR's changes?