Skip to content
This repository has been archived by the owner on Dec 19, 2024. It is now read-only.

Allow to run plugins before transformation (eg: plug a linter, run non-w3c like transformations) #149

Closed
MoOx opened this issue Jun 4, 2015 · 8 comments · Fixed by #238

Comments

@MoOx
Copy link
Owner

MoOx commented Jun 4, 2015

Ref postcss/postcss-import#45
stylelint will be actively supported.

@Globegitter
Copy link

Looking forward to seeing that implemented :)

@magsout
Copy link
Contributor

magsout commented Jul 13, 2015

Good.I'm trying to use stylelint

@MoOx
Copy link
Owner Author

MoOx commented Jul 13, 2015

For now you should be able to use the postcss-import plugins option to lint all imported files. We still need to find a way to apply some plugins to all input (main input passed to postcss + imported files using the previously mentioned postcss-import option) before transformations.

What about we create an option to do that? Here is some ideas for the name (most are shitty but you know, naming is not the easiest thing):

  • pluginsOnEachInput
  • pluginsForEachInputs
  • onInputPlugins
  • beforeProcessPlugins
  • beforeProcessPlugins
  • preTransformationPlugins
  • preTransformPlugins
  • prePlugins

Any smarter ideas are welcome :)

@kewah
Copy link

kewah commented Jul 16, 2015

what about beforeTransform ? as you said it's before transformations

@MoOx
Copy link
Owner Author

MoOx commented Jul 16, 2015

Since it's a plugins array, maybe it should contains "plugins" in the option name.
beforeTransformPlugins is long, but clear.

@kewah
Copy link

kewah commented Jul 16, 2015

👍
beforeTransform sounds better for a callback but not for an array

@magsout
Copy link
Contributor

magsout commented Jul 16, 2015

beforeTransformPlugins

lgtm 👍

@MoOx MoOx changed the title Allow to plug a linter Allow to run plugins before transformation (eg: plug a linter, run non-w3c like transformations) Jul 27, 2015
@MoOx MoOx mentioned this issue Dec 29, 2015
5 tasks
@MoOx MoOx closed this as completed in #238 Jan 4, 2016
@MoOx
Copy link
Owner Author

MoOx commented Jan 4, 2016

Not relevant anymore. cssnext is now postcss-cssnext. cssnext is deprecated. See postcss-cssnext migration guide http://cssnext.io/postcss/

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants