-
-
Notifications
You must be signed in to change notification settings - Fork 188
Rename from/to options to source/dest ? #160
Comments
Where possible it would be good to be consistent with what the rest of the PostCSS ecosystem is doing. I think any such change should be in PostCSS itself to maintain that consistency. |
These options are only relevant if you are using cssnext directly, not through postcss. So not sure if it's a requirement. But if @ai is open to this kind of improvement, why not. |
Yep, but it is nicer if all of our modules use the same options for source maps; so that if a user of a PostCSS module wants source maps, she doesn't have to apply different options when wanting to use cssnext instead. 😄 |
I don't consider cssnext as a postcss plugin (mostly because I think most people should not use postcss directly - like babel user that don't use acorn directly). |
@MoOx I understand you, but without a main PostCSS runner there will not be a way for small and new plugins for developer. We will stagnation. |
I am not sure about what you are saying @ai. |
My idea is that if user use gulp-postcss, instead of postcss autoprefixer or gulp-cssnext, he can add also many other small PostCSS plugins, like postcss-data-packer. So market will be open for new ideas. With gulp-autoprefixer it is psychology more difficult to add new plugin for user. |
cssnext now have a plugin option to pipe others plugins :) |
We can rename it, of course. But why they are better? It is only question of taste our there is any objective benefits. What Babel uses? |
Babel don't have this kind of options. |
Should be a postcss issue. |
I always found
from
&to
option where pretty shitty and I am not sure we should keep them.We might introduce this change in a major release.
Any thoughts ?
The text was updated successfully, but these errors were encountered: