-
-
Notifications
You must be signed in to change notification settings - Fork 731
fix(css): allow navigation property for view-transition (fixes #7340) #7352
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
Changes from all commits
673d5b2
8447596
faeedc7
955b1db
b8a9211
663426b
af97d7f
ff39272
f0cf1c2
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,7 @@ | ||
| --- | ||
| "@biomejs/biome": patch | ||
| --- | ||
|
|
||
| Fixed [#7286](https://github.com/biomejs/biome/issues/7286). Files are now formatted with JSX behavior when `javascript.parser.jsxEverywhere` is explicitly set. | ||
|
|
||
| Previously, this flag was only used for parsing, but not for formatting, which resulted in incorrect formatting of conditional expressions when JSX syntax is used in `.js` files. | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,18 @@ | ||
| --- | ||
| "@biomejs/biome": patch | ||
| --- | ||
|
|
||
| Fixed [#7310](https://github.com/biomejs/biome/issues/7310): [`useReadonlyClassProperties`](https://biomejs.dev/linter/rules/use-readonly-class-properties/) correctly handles nested assignments, avoiding false positives when a class property is assigned within another assignment expression. | ||
|
|
||
| Example of code that previously triggered a false positive but is now correctly ignored: | ||
|
|
||
| ```ts | ||
| class test { | ||
| private thing: number = 0; // incorrectly flagged | ||
|
|
||
| public incrementThing(): void { | ||
| const temp = {x: 0}; | ||
| temp.x = this.thing++; | ||
| } | ||
| } | ||
| ``` | ||
|
Comment on lines
+1
to
+18
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🛠️ Refactor suggestion Changeset content does not match this PR’s scope (navigation property). Replace with a changeset for noUnknownProperty. This PR fixes a CSS false positive for Proposed replacement: ---
-"@biomejs/biome": patch
----
-
-Fixed [#7310](https://github.com/biomejs/biome/issues/7310): [`useReadonlyClassProperties`](https://biomejs.dev/linter/rules/use-readonly-class-properties/) correctly handles nested assignments, avoiding false positives when a class property is assigned within another assignment expression.
-
-Example of code that previously triggered a false positive but is now correctly ignored:
-
-```ts
-class test {
- private thing: number = 0; // incorrectly flagged
-
- public incrementThing(): void {
- const temp = {x: 0};
- temp.x = this.thing++;
- }
-}
-```
+ "@biomejs/biome": patch
+---
+
+Fixed [#7340](https://github.com/biomejs/biome/issues/7340): `noUnknownProperty` recognises the CSS `navigation` property from the View Transitions spec, avoiding false positives.
+
+Example (valid, no diagnostics):
+
+```css
+.card {
+ navigation: auto;
+}
+```I can also open a new changeset file with the correct name and remove this one if you prefer. |
||
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.
Changeset appears unrelated to this PR and misses a trailing full stop.
This PR targets CSS “navigation” property support; this changeset is about JSX-everywhere formatting and links #7286. Either move it to the relevant PR or adjust the content. Also, per repo guidelines, end sentences with a period.
🤖 Prompt for AI Agents