Yannick Decat

@bitwiseman @mklueh I found out where it was problematic : js/src/css/beautifier.js line 375 ``` if ((insideRule || enteringConditionalGroup) && !(this._input.lookBack("&") || this.foundNestedPseudoClass()) && !this._input.lookBack("(") && !insideAtExtend && parenLevel === 0)...

@romainmenke Is this behaviour working fine with a line like this ? : ``` h3 { @extend .btn-blue:hover; } ``` the result is this ? ``` h3 { @extend .btn-blue:...

`@extend`, `@import`, `@apply` are not standard CSS but they follow the css at rules syntax, they are custom at rules. `@media`, `@page`, `@font-face`, etc in the other hand are css...

@bitwiseman, let's try this out. I'll add a new test in the css/tests.js file : ``` unchanged: [ 'h3 {', ' @apply flex flex-col lg:flex-row space-y-3 lg:space-x-12 items-start;', '}' ]...

@floroz It isn't yet approved by VSCode. We will have to wait this PR to be merged : https://github.com/microsoft/vscode-css-languageservice/pull/354#pullrequestreview-1553275626. You're actually on the js-beautify repository, where it has been approved,...

Also, schema for `no-sequences` is missing `type : "object"` in one place. The configuration should be invalid(`"foo"` should be an object): ``` "no-sequences": ["error", "foo"] ```

@mdjermanovic I tried both schemas and you're indeed right, the suggested schema does not work. I was actually focused on the `type: array` thing. I should have noticed its importance...

in `new-parens` , `schema` is an object. it should be an array depending on documentation : ``` schema (array) specifies the [options] so ESLint can prevent invalid [rule configurations] ```...

@mdjermanovic I will. I am on it.

Hi @austintoddj, I know it's been quite some time here. Do you want me to do something here or this is related to the V7?