Right now we can create custom configuration based on presets, however I think it would be worth allowing custom presets also.
This would mean opening up the Preset interface so for example a framework could maintain their own Preset file and users can then use the preset, just by pointing

It seems configurations for proselint are centralized to different canonical files (namely $XDG_CONFIG_HOME/proselint/config, ~/.config/proselint/config and ~/.proselintrc) instead of a per project config basis.

So may I ask how to specify project/folder/files-specific rules? Maybe including some examples in the README.md would be nice?

Thanks

In order to make the Tailwind preset more approachable for people that already know Tailwind, we should:

• Font sizes should have the same aliases (e.g. lg = 2)
• Colors should be aliased to the same aliases * 100, e.g. purple.5 === purple.500
• Breaking change for a major version: Make the padding scale match Tailwind's

One of the consumers of our system uses curly braces for content replacement in strings.

Due to the way that SD currently uses curly braces in the build process there is no way I can have a string that includes the braces for consumption.

I have tried a number of ways to escape the braces with no luck

Other languages and templating systems seem to use the concept of using double curly b

The following warnings appear in the console during compilation, and they are also shown by stylable intelligence:

WARNING in Stylable: "@st-scope" must receive a simple selector, but instead got: ":global(.foo)"
@st-scope :global(.foo) { }

WARNING in Stylable: "@st-scope" received an unknown symbol: "html"
@st-scope html { }

The compiled CSS works correctly, though.

While still useful outside of Rails, Timecop has its downsides, one is that it's not thread-safe.

AS already has what Timecop provides, freeze_time, travel, travel_back, travel_to.

@page has special rules here: https://developer.mozilla.org/en-US/docs/Web/CSS/@page

This is similar to @viewport which already has a custom type Viewport.

export interface Viewport<TLength = string | 0> {
  msHeight?: ViewportHeightProperty<TLength>;
  msMaxHeight?: ViewportMaxHeightProperty<TLength>;
  msMaxWidth?: ViewportMaxWidthProperty<TLength>;
  msMaxZoom?: ViewportMax

A PR for redpotion came in to clean this same kind of code up - we should modify our color method that uses pointers here

to match what was done there: infinitered/redpotion#127

• Add space-evenly and potentially others to justify-content (https://developer.mozilla.org/en-US/docs/Web/CSS/justify-content)
• Add break-word and potentially others to word-break (https://developer.mozilla.org/en-US/docs/Web/CSS/word-break)

Locations for a fix:
https://github.com/CSSLint/parser-lib/blob/master/src/css/Properties.js#L290
and https://github.com/CSSLint/parser-lib