feat(dev-lib): enable no-nested-ternary oxlint rule - #154
Merged
Conversation
Rewrites the 8 nested ternary expressions across js-lib, nodejs-lib, backend-lib and datastore-lib as early returns or if/else. Pure readability change, behaviour is identical. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DXP6cFK7Mu2Jdh487AXmTc
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DXP6cFK7Mu2Jdh487AXmTc
kirillgroshkov
approved these changes
Sep 1, 2026
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
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.
Turns on the
no-nested-ternaryoxlint rule in the shared config.Stacked on #153, which clears the existing violations here; GitHub will retarget this to
mainonce that merges. Consumers should be clean before picking up the new dev-lib version.