Repository navigation
style: fold enum-fix ternary onto one line - #3
Merged
Merged
Conversation
The enum-object-form fix landed on top of an already-formatted file, so the new ternary survived in its longhand form and tripped Lint on main after #1 merged. Pure prettier --write, no behavior change.
There was a problem hiding this comment.
Pull request overview
This PR restores lint cleanliness by applying prettier --write formatting to a single ternary expression used when deriving an enum reference name in EntitySchemaRenderer, with no intended behavior change.
Changes:
- Reformats the enum constructor-name fallback ternary into a single line (prettier output).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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.
Summary
prettier --writeon a single ternary; no behavior change.Test plan
npm run lintcleannpm test— 35/35 passing