Is there a config option to disable invalid property warnings?

[corysimmons]

I make PostCSS plugins that use invalid properties.

I intentionally namespace them (e.g. lost-columnd: 1/2) so there's virtually zero chance they'll ever conflict with W3C.

Is it possible to disable invalid property warning via .stylintrc?

Or, even better, would it be possible to make it so you can ignore a namespace? (I plan on making a lot of these foo- libraries in the coming months.

[rossPatton]

there is actually!

technically, it's to be used with transparent mixins, but you should be able to use them with custom properties as well.

i see now that while it's mentioned in the docs, it's not in the example config (and the naming apparently could be better)

in your .stylintrc or options config just do:

{
  mixins: ['lost-columnd']
}

lemme know if that works

[corysimmons]

Is that just an array of each property? It might get pretty hairy having to manually type in dozens of properties. Is it possible to throw a little regex in there?

{
  mixins: ['lost-'*]
}

I know this seems specific, but I really am about to drop a bunch of tools that do this kinda stuff and I <3 Stylus.

[rossPatton]

yeah, it was just a quick and dirty fix for another user who wanted transparent mixins to not trip the invalid property rule. i could look into using regex for it.

[corysimmons]

That'd be awesome, thanks!

[fdeneux]

+1 That would be awesome indeed.

[PhiLhoSoft]

there is actually! technically, it's to be used with transparent mixins, but you should be able to use them with custom properties as well.

Some remarks:

• This is not mentioned at all in https://rosspatton.github.io/stylint/ Apparently, this page is out of date with regard to the readme...
• transparent mixins / custom properties ( Array ) only mentions customProperties, we have to go to Options to see "Note that customProperties and mixins are aliases"...
• I am glad you added this (and that I stumbled upon this issue) because I have to add "customProperties": [ "-webkit-text-stroke-color", "-webkit-text-stroke-width" ], to get rid of a very annoying range of spurious warnings. I suggest to add these two browser-dependent properties to your linter, BTW.

It might get pretty hairy having to manually type in dozens of properties.

Yes, but on the other hand, it prevent typos, which is the point of this setting. :smile: Akin to your remark, I might benefit from giving "-webkit-text-stroke-*" but then I can get no warning on -webkit-text-stroke-widht for example. Not against the suggestion (we are free to avoid regexes anyway), just a heads up. :wink: