-
-
Notifications
You must be signed in to change notification settings - Fork 717
chore: fix typos in biome css analyze crates #7187
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
Conversation
|
WalkthroughRenamed six Rust test functions from test_kown_properties_order to test_known_properties_order across edge, explorer, firefox, safari, samsung internet, and US browser property groups. Test bodies unchanged. In CSS test fixtures, corrected opactity to opacity in both invalid.css and valid.css for the .example-from-doc-comment rule. Added a trailing newline to valid.css. No changes to underlying data or public APIs. Suggested labels
Suggested reviewers
✨ Finishing Touches
🧪 Generate unit tests
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
8df3b60
to
78d20fd
Compare
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.
Actionable comments posted: 0
🧹 Nitpick comments (1)
crates/biome_css_analyze/src/keywords.rs (1)
5949-5953
: Optional consistency: align naming and style with other “sorted” testsMost tests here use is_sorted or compare against a sorted copy; these six use windows(2). Both are fine, but consider renaming to ..._sorted and using the same style for consistency.
Example tweak:
-#[test] -fn test_known_edge_properties_order() { - for items in KNOWN_EDGE_PROPERTIES.windows(2) { - assert!(items[0] < items[1], "{} < {}", items[0], items[1]); - } -} +#[test] +fn test_known_edge_properties_sorted() { + let sorted = KNOWN_EDGE_PROPERTIES.to_vec(); + let _ = sorted.is_sorted(); + assert_eq!(KNOWN_EDGE_PROPERTIES, sorted.as_slice()); +}
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (2)
crates/biome_css_analyze/tests/specs/source/useSortedProperties/invalid.css.snap
is excluded by!**/*.snap
and included by**
crates/biome_css_analyze/tests/specs/source/useSortedProperties/valid.css.snap
is excluded by!**/*.snap
and included by**
📒 Files selected for processing (3)
crates/biome_css_analyze/src/keywords.rs
(1 hunks)crates/biome_css_analyze/tests/specs/source/useSortedProperties/invalid.css
(1 hunks)crates/biome_css_analyze/tests/specs/source/useSortedProperties/valid.css
(2 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
crates/biome_*/**/*
📄 CodeRabbit Inference Engine (CLAUDE.md)
Core crates must be located in
/crates/biome_*/
Files:
crates/biome_css_analyze/tests/specs/source/useSortedProperties/valid.css
crates/biome_css_analyze/src/keywords.rs
crates/biome_css_analyze/tests/specs/source/useSortedProperties/invalid.css
**/*.{rs,toml}
📄 CodeRabbit Inference Engine (CLAUDE.md)
Format code (Rust + TOML) using
just format
Format Rust and TOML files before committing (use
just f
/just format
).
Files:
crates/biome_css_analyze/src/keywords.rs
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (24)
- GitHub Check: Documentation
- GitHub Check: Lint project (depot-ubuntu-24.04-arm-16)
- GitHub Check: Check Dependencies
- GitHub Check: Test (depot-windows-2022-16)
- GitHub Check: Lint project (depot-windows-2022)
- GitHub Check: Test (depot-ubuntu-24.04-arm-16)
- GitHub Check: Test Node.js API
- GitHub Check: Bench (biome_html_formatter)
- GitHub Check: Bench (biome_graphql_formatter)
- GitHub Check: Bench (biome_module_graph)
- GitHub Check: Bench (biome_configuration)
- GitHub Check: Bench (biome_package)
- GitHub Check: Bench (biome_css_parser)
- GitHub Check: Bench (biome_json_formatter)
- GitHub Check: Bench (biome_graphql_parser)
- GitHub Check: Bench (biome_json_analyze)
- GitHub Check: Bench (biome_html_parser)
- GitHub Check: Bench (biome_js_analyze)
- GitHub Check: Bench (biome_js_parser)
- GitHub Check: Bench (biome_css_analyze)
- GitHub Check: Bench (biome_css_formatter)
- GitHub Check: Bench (biome_json_parser)
- GitHub Check: autofix
- GitHub Check: Bench (biome_js_formatter)
🔇 Additional comments (4)
crates/biome_css_analyze/tests/specs/source/useSortedProperties/invalid.css (1)
72-72
: Typo fix looks spot onGood catch switching opactity to opacity; keeps the fixture meaningful without changing test intent.
crates/biome_css_analyze/tests/specs/source/useSortedProperties/valid.css (2)
79-79
: Corrected 'opacity' in transitionNice one. This keeps the “valid” example actually valid and aligned with the docs.
106-106
: Trailing newline addedTiny but tidy. This keeps editors and linters happy.
crates/biome_css_analyze/src/keywords.rs (1)
5949-5949
: Renaming tests kown -> known: LGTMThanks for the polish. Names now read cleanly; no behavioural change to the assertions.
Also applies to: 5956-5956, 5963-5963, 5970-5970, 5977-5977, 5984-5984
CodSpeed Performance ReportMerging #7187 will not alter performanceComparing Summary
Footnotes |
Summary
Fix typos in biome_css_analyze tests and CSS fixtures
Tests:
sumsung
tosamsung
Test Plan
cargo test