fix: prettier integration broken due to nullish coalescing misuse #836
+19
−1
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
Fixes xojs#834 Replace ?? with || in prettier validation logic to properly detect semicolon conflicts between XO and Prettier configurations.
spence-s
approved these changes
Sep 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Fixes #834
Problem
Prettier integration fails to disable stylistic rules due to incorrect boolean logic using
??instead of||.Root cause
Line 77 uses nullish coalescing for boolean evaluation, causing validation to never trigger.
Fix
Replace
??with||for proper boolean OR logic.Testing
Added test case to verify validation correctly detects semicolon conflicts.