kevscript / vscolors Goto Github PK

When I highlight rgba(10 10 10 / 10%), right-click, and choose "Color to HSL", I get an error saying "Can't resolve color format of rgba(10 10 10 / 10%)".

I have to change it to the legacy format rgba(10, 10, 10, 0.1), at which point I can convert it. It generates hsla(0, 0%, 4%, 0.1), which is also the legacy format.

But this generates a Stylelint violation "Expected 0.1 to be 10% (alpha-value-notation)". If I make that change, I get "Expected modern color-function notation (color-function-notation)".

Stylelint is expecting the modern format: hsla(0deg 0% 4% / 10%); examples are at the link above. (It appears that the deg is required by a separate rule: hue-degree-notation.)

Would it be possible for the extension to:

1. read the modern formats, and
2. have an option to write colours in the modern formats rather than the legacy ones? (It would probably be a good idea to have a second option to control whether to use deg in angles, too.)

Hey @kevscript, how are you?
Great extension, it's the only color format converter
that really worked perfectly for me.

I'm having a bit of trouble with HEX colors.
When you double click a text to select the color to convert,
VS Code does not include the hashtag character.

Example:

Double click the string:

"#C9533E",

Right click, convert to RGB:

Do you think it would be possible to:
remove the '#' character from the regex,
when converting back, replace the selection + 1 character to the left?

Since 'rgb' and 'hsl' both have the name strings before,
it's very distinguishable from HEX colors, it could work.

If you think it's a good idea or there's a better solution, let me know and I can PR it. =)