Add a new array to config file specifying to minimum requirements.

Details

Right now the min requirements can only be supplied as running arguments, however as the same values are often required for these, I think they should be added to the config file.

Our Configuration class should

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

Based on the discussions around #121 and the test we just merged in #662, we are going to convert theme-ui to TypeScript! 🎉 The plan is to go package-by-package and gradually move all .js files to .ts files.

Currently we only provide documentation for consuming the existing custom-values offered by Stylable, stMap, stArray and if you explicitly import it stBorder.

Need to add the relevant documentation to both the package readme and to the stylable.io.

Based on this CSS-Tricks article lets remove bad words from the documentation. Words/phrases to remove:

• just
• simply
• clearly
• of course
• easy
• so
• basically
• technically
• very
• in order to
• everyone knows

One thing to note, some markdown files are generated by a script and handlebars, but those h

Hey, everyone!

described_class is no doubt widely used in specs, there are 1376 usages in repositories listed in real-world-ruby-apps.

According to described_class docs:

If the first argument to [...] example group is a class, the class is exposed

According to MDN, text-decoration requires no browser prefixes except for when used with a shorthand property in Safari browsers, when it needs the -webkit- prefix.

From what I can tell, the current types don't allow for the -webkit- prefix for text-decoration.

Right now, we decide if one single comment line is definitely not plain English given its first character, and then decide not to add a space prefix to it.

If that's the case, the same should apply to its whole "paragraph", i.e. the consecutive comment lines (before or after) which aren't empty.

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

The diagnostics provieded in the debug console when an error occurs is not precise enough.
aserts in the constructor and debugFillProperties should be implemented for better diagnistocs.

Look at the AnimatedContainer widget source code for examples.