aeschli / vscode-css-formatter Goto Github PK

Is it possible to customize this css document formatting extension's alt+shift+f triggered formatting behaviors such that . . .

1. reformatting of decedent selectors [ .someclass > * ] doesn't uses spaces vs stripping them out as it currently does [ .someclass>* ] ?

2. reformatting of inline comments [ flex: 1; /* using this to achieve blahblah / ] doesn't kick the inline comment to its own separate line [ [ flex: 1; \n\r / using this to achieve blahblah */ ] ?

Alternatively are the above two reformatting behaviors based on some css document formatting standards that address browser parsing issues or following some well accepted standard and should be kept as is?

Range format should not make changes outside range

I installed this plugin but there is no manual.

using this particular css:

filter: progid:DXImageTransform.Microsoft.gradient(enabled=false);

if you format you get a space between progid and DXImageblabla

filter: progid: DXImageTransform.Microsoft.gradient(enabled=false);

and this breaks the less compilation.

• Extension Name: vscode-css-formatter
• Extension Version: 1.0.1
• OS Version: Windows_NT x64 10.0.16299
• VSCode version: 1.28.0

We have written the needed data into your clipboard. Please paste:

This extension is still using JS-Beautify 1.7.4 whereas the latest version is 1.10.2

By simply updating this dependency a lot of bugs would be fixed.

One bug I've encountered that drives me crazy is that using grid-template-areas with input like this:

body {
	grid-template-areas:
		"aa aa aa"
		"bb bb bb";
}

Results in something like this after formatting:

body {
	grid-template-areas:"aa aa aa" "bb bb bb";
}

Issues like this have been fixed in js-beautify already so it would be ideal to have that updated

Hi,

since the 1.18 update of VSCode, CSSFormatter is not working.
I always get this message

Type: Bug

in my website colour used by css is not shown and some more features of css are not working in my website

Extension version: 1.0.2
VS Code version: Code 1.76.2 (ee2b180d582a7f601fa6ecfdad8d9fd269ab1884, 2023-03-14T17:55:54.936Z)
OS version: Windows_NT x64 10.0.19044
Modes:
Sandboxed: Yes

vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vsdfh931cf:30280410
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdc:30486549
c4g48928:30535728
dsvsc012:30540252
pynewvextcfv2:30681851
azure-dev_surveyone:30548225
pyindex848:30662994
nodejswelcome1cf:30587006
3biah626:30602489
pyind779:30671433
f6dab269:30613381
pythonsymbol12:30671437
vsctsb:30677850
functionswalk:30687959
pythonms35:30686772

👋 Hi there, Martin here, from the VS Code team.

Recently we've announced the Remote Repository feature that lets you browse and edit files and folders directly on GitHub.

Open Remote Repository... opens VSCode on a folder or workspace located on a virtual file system. We call this a virtual workspace. We observed that not all extension support this well, either because they can not, or they haven't thought about it.

It would be fantastic if you could test whether your extension can handle virtual workspaces:

Check out the Virtual Workspaces Extension Author Guide on how to do that.

When done, set the new virtualWorkspaces capability in your 'package.json'.

{
  "capabilities": {
    "virtualWorkspaces": true | false
  }
}

• Use "virtualWorkspaces": true if your extension is prepared for virtual workspaces
• Use "virtualWorkspaces": false if your extension should be disabled when a virtual workspace is opened

For questions and comments please use the Virtual Workspaces Tracking Issue.

Thanks for the support and the great work! ❤️

Is the project still being maintained?
Please let us know, it's important for people that use this extension

Hello,

It would be nice if you could add support for SCSS files. Please

Type: Feature Request

ok

Extension version: 1.0.2
VS Code version: Code 1.76.0 (92da9481c0904c6adfe372c12da3b7748d74bdcb, 2023-03-01T10:22:44.506Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: Yes

When a css file applies a tailwind class e.g. @apply focus:outline-none; the formatter reformats as @apply focus: outline-none; which is incorrect.

After installing this extention, folders can not be renamed via Explorer in VS Code's Side Bar. After disabling this extention, problems disappear. VS Code version is 1.41.1

Hello,
I see issue with @media () {} - doesn't keep empty lines inside.
Let me know if you need more complex example

When using CSS Modules I sometimes use :global inside my CSS selector to access global class names instead of local ones.

Example:

.row :global .icon {
    border: 1px solid #ff0000;
}

Your formatter removes the space before :global which is not permitted.

I'm looking to have this css formatter extension behave like the oob html document formatting support where alt+shift+f will trigger a formatting of entire document or selected content. Is that possible?

This extension doesn't support user configuration. It would be nice if you could set some options in vscode's settings.json.