You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
assetsStatic files, components defining or contributing to appearancetoolingTools, workflows, integrations etc. relevant to project maintenance, deployment, collaboration
We use a new workflow for formatting CSS in external files, whose configuration is not done via pyproject.toml or similar but which seems to solely rely on command line arguments.
@gythaogg and I went through #1262 together yesterday, which took a lot longer than expected because the formatter's error reporting is not helpful and the config is not transparent.
It would be preferable if the tool were set up to work like the existing ones (Ruff, djLint etc.), which would also help with building on or tweaking the Core config for our own projects/local development.
assetsStatic files, components defining or contributing to appearancetoolingTools, workflows, integrations etc. relevant to project maintenance, deployment, collaboration
We use a new workflow for formatting CSS in external files, whose configuration is not done via pyproject.toml or similar but which seems to solely rely on command line arguments.
@gythaogg and I went through #1262 together yesterday, which took a lot longer than expected because the formatter's error reporting is not helpful and the config is not transparent.
It would be preferable if the tool were set up to work like the existing ones (Ruff, djLint etc.), which would also help with building on or tweaking the Core config for our own projects/local development.
Related: #1326
The text was updated successfully, but these errors were encountered: