darwintantuco / stylelint-8-point-grid Goto Github PK

e.g.
width: calc(100% - 60px)

Update regex, use ^

You can use PostCSS to add custom properties. This plugin can't check custom properties. For example size properties in postcss-short. You also don't have any logical CSS properties: margin-block, margin-block-start, margin-block-end, margin-inline, margin-inline-start, margin-inline-end, margin-start, margin-end and etc.

Hi,

Adding support for CSS Logical Properties was previously mentioned in issue #28, but I feel a separate tracking issue is warranted, as logical properties are well-defined and widely supported, and the scope of that issue is much larger. Logical properties allow for spacing and layout to automatically adjust based on the writing system, and the number of logical properties (such as padding-inline-start and margin-block-end, which for English pages correspond to padding-left and margin-bottom) is similar to the exisiting number of positional properties.

The simplest option would be to add the logical properties corresponding to supported physical properties to the supportedCssProperties array. If you like, I'd be happy to write up a pull request with the modifications and tests. Otherwise, let me know if you need more info.

Please support stylelint 16.0.0, the big one

Now the code is in ESM instead of CommonJS

Very good

Stylelint team published docs to know how to migrate with ease.

No need to keep support to commons from now on.

Style lint 16 is not allowed in your package.json. remove this restriction to

Is there any specific reason why border property can not be ignored?
If it is possible in theory I could make a PR to support that 🙂

whitelist -> allowlist (api)
blacklist -> ignorelist

We use rem in our codebase instead of px, which has a lot of benefits. To illustrate, 1rem equals 16px at a 16px root font size. To align with the 8pt grid, we therefor need to use e.g. a base of 0.5 to make sure every rem value is divisible by 0.5, i.e. 0.5rem=8px, 1rem=16px, 1.5rem=24px etc. If we want, we can use a different font-size between the marketing page and the application and the grid and stylelint config will scale automatically.

This was possible in 0.2.4, but 0.2.5 enforced that base must be a multiple of 1, breaking this use case. Is there a reason for that requirement?

https://github.com/darwintantuco/stylelint-8-point-grid/blob/bf3ab78bd6cd347074c73119ca8b8ec6e91f33c8/src/utils.ts#L3:14