Jon

Results 49 comments of Jon
trafficstars

I took a look at this thinking it would be a relatively simple solve, but it turns out this is going to be pretty complicated to solve properly. For anyone...

I'm working on Comment Placement now

Agreed, the parser is pretty far along, but there will be many changes before it can effectively lint full CSS files (for example, we're adding parsing for exact properties now,...

> what are your plans/thoughts about SCSS? It's unlikely that we'll add any non-standard CSS dialects in the short term. SCSS and other dialects like Less and even PostCSS end...

I created #1359 to track implementing the CSS-wide keywords as tokens and making them invalid as custom identifiers.

I've gotten part way through implementing some infrastructure to enable exact parsing of individual properties, but I'm realizing that it will require some changes to the parser itself to support...

> assuming the way its done in the border one is close to final, I could work on implementing it for the rest @Gami13 as Denis mentioned, after investigating with...

I was just looking at this yesterday, and I think this is sort of similar to the case of multiple access modifiers on a typescript method, like: ```typescript class Foo...

> When running `biome format . --write` or `biome check . --apply`, biome should automatically remove the trailing , in JSON files. I think this is reasonable. When running with...

Simplifying this down to the base case: [Playground Link](https://biomejs.dev/playground/?code=bABvAG4AZwBDAG8AbgBkAGkAdABpAG8AbgBFAHgAcAByAGUAcwBzAGkAbwBuADEACgAgACAAPwAgAGMAbwBuAHMAZQBxAHUAZQBuAHQAMQAKACAAIAA6ACAAbABvAG4AZwBDAG8AbgBkAGkAdABpAG8AbgBFAHgAcAByAGUAcwBzAGkAbwBuADIACgAgACAAIAAgAD8AIABjAG8AbgBzAGUAcQB1AGUAbgB0ADIACgAgACAAIAAgADoAIABsAG8AbgBnAEMAbwBuAGQAaQB0AGkAbwBuAEUAeABwAHIAZQBzAHMAaQBvAG4AMwAKACAAIAAgACAAIAAgAD8AIABjAG8AbgBzAGUAcQB1AGUAbgB0ADMACgAgACAAIAAgACAAIAA6ACAAYwBvAG4AcwBlAHEAdQBlAG4AdAA0AAoA) ```typescript longConditionExpression1 ? consequent1 : longConditionExpression2 ? consequent2 : longConditionExpression3 ? consequent3 : consequent4 // Prettier 3.1 output longConditionExpression1 ? consequent1...