New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Official file extension #8

Closed
ai opened this Issue Jul 13, 2015 · 10 comments

Comments

Projects
None yet
4 participants
@ai

ai commented Jul 13, 2015

Mayb we should select official file extension for PreCSS source (or any PostCSS sources with custom CSS).

What about .pcss?

@hudochenkov

This comment has been minimized.

Show comment
Hide comment
@hudochenkov

hudochenkov Jul 14, 2015

I like .pcss. With official file extension for all CSS contains PostCSS stuff it will be easier for editors and other tools to detect syntax highlighting and other syntax related things.

@ai, maybe you should open this issue in postcss/postcss?

hudochenkov commented Jul 14, 2015

I like .pcss. With official file extension for all CSS contains PostCSS stuff it will be easier for editors and other tools to detect syntax highlighting and other syntax related things.

@ai, maybe you should open this issue in postcss/postcss?

@ai

This comment has been minimized.

Show comment
Hide comment
@ai

ai Jul 14, 2015

@hudochenkov cssnext or autoprefixer doesn’t need any file ext because they work with plain CSS.

ai commented Jul 14, 2015

@hudochenkov cssnext or autoprefixer doesn’t need any file ext because they work with plain CSS.

@hudochenkov

This comment has been minimized.

Show comment
Hide comment
@hudochenkov

hudochenkov Jul 14, 2015

@ai but many other plugins aren't W3C standards compatible.

hudochenkov commented Jul 14, 2015

@ai but many other plugins aren't W3C standards compatible.

@ai

This comment has been minimized.

Show comment
Hide comment
@ai

ai Jul 14, 2015

@hudochenkov what plugins you can remember outside the PreCSS? ;)

ai commented Jul 14, 2015

@hudochenkov what plugins you can remember outside the PreCSS? ;)

@ai

This comment has been minimized.

Show comment
Hide comment
@ai

ai Jul 14, 2015

@hudochenkov each and for is in PreCSS, other should be moved there too.

ai commented Jul 14, 2015

@hudochenkov each and for is in PreCSS, other should be moved there too.

@jedmao

This comment has been minimized.

Show comment
Hide comment
@jedmao

jedmao Jul 18, 2015

@ai if these plugins can be parsed by a CSS parser, then, in a way, are they not valid CSS? In other words, what exactly do we mean by valid CSS?

jedmao commented Jul 18, 2015

@ai if these plugins can be parsed by a CSS parser, then, in a way, are they not valid CSS? In other words, what exactly do we mean by valid CSS?

@jedmao

This comment has been minimized.

Show comment
Hide comment
@jedmao

jedmao Jul 19, 2015

Also, @ai, did you anticipate this happening with PostCSS plugins or does this deviate, somehow, from the original project scope? I'm just curious what your philosophy is here.

jedmao commented Jul 19, 2015

Also, @ai, did you anticipate this happening with PostCSS plugins or does this deviate, somehow, from the original project scope? I'm just curious what your philosophy is here.

@ai

This comment has been minimized.

Show comment
Hide comment
@ai

ai Jul 19, 2015

Technically, custom at-rule is not part of W3C CSS. File is still valid, but content of this at-rule will be ignored.

ai commented Jul 19, 2015

Technically, custom at-rule is not part of W3C CSS. File is still valid, but content of this at-rule will be ignored.

@jonathantneal

This comment has been minimized.

Show comment
Hide comment
@jonathantneal

jonathantneal Sep 14, 2015

Owner

I’m not convinced a custom syntax is warranted. I’d rather see a plugin for Sublime or Atom that uses PostCSS to handle the formatting, agnostic to precss.

Owner

jonathantneal commented Sep 14, 2015

I’m not convinced a custom syntax is warranted. I’d rather see a plugin for Sublime or Atom that uses PostCSS to handle the formatting, agnostic to precss.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment