Back to all reviewers

CSS comment standards

logseq/logseq
Based on 2 comments
Css

Always use proper CSS comment syntax (`/* */`) instead of inline comments (`//`) for better cross-browser compatibility and code consistency. Additionally, rely on autoprefixer configuration for vendor prefixes rather than manually adding them, which reduces code duplication and maintenance overhead.

Code Style Css

Reviewer Prompt

Always use proper CSS comment syntax (/* */) instead of inline comments (//) for better cross-browser compatibility and code consistency. Additionally, rely on autoprefixer configuration for vendor prefixes rather than manually adding them, which reduces code duplication and maintenance overhead.

Example of proper CSS commenting:

/* Good: Proper CSS comment syntax */
right: 10px; /* Allows clicking on the scrollbar */

/* Avoid: Inline comment syntax */
right: 10px; // Allows clicking on the scrollbar

For vendor prefixes, configure autoprefixer at the project level instead of manually adding prefixes:

/* Good: Let autoprefixer handle this */
user-select: none;

/* Avoid: Manual vendor prefixes when autoprefixer is available */
-webkit-user-select: none;
-khtml-user-select: none;
-moz-user-select: none;
-ms-user-select: none;
user-select: none;

This approach ensures consistent formatting, reduces maintenance burden, and leverages build tools effectively for better code organization.

2
Comments Analyzed
Css
Primary Language
Code Style
Category

Source Discussions