chore: version packages#33
Merged
Merged
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
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@gaia-react/lint@1.7.0
Minor Changes
#32
55bb692Thanks @stevensacks! - Flag renderingnullfrom a JSX ternary viano-restricted-syntax.cond ? <JSX/> : nullandcond ? null : <JSX/>are nowerror-level. Bothare the boolean-guarded
&&render guard written the long way; usecond && <JSX/>instead (coerce a numeric/falsy guard with!!condso the0value can't leak into the output).The selectors are flag-only, with no autofix: a blind
? : null→&&rewriteis unsafe because numeric-
0guards need!!,??-fed values need: undefined, and||-guards need per-operand coercion. A human applies thefix the selector points to.
Both selectors only match a
JSXElement/JSXFragmentbranch, so they areinert outside
.tsx/.jsx. Allno-restricted-syntaxselectors areconsolidated into one
gaia/no-restricted-syntaxconfig object, because ESLintflat config merges that rule key by replacement (last match wins), not
concatenation.
A consumer with a
cond ? <JSX/> : nullternary will see a NEW lint failure onupgrade. That is the intent: convert it to
&&.