Suport for alternative PostCSS syntaxes

[jonathantneal]

Added: support for alternative PostCSS syntaxes

[MoOx]

I don't understand what this is about. Care to add a test?

[ai]

PostCSS 6.0 has custom parsers. So user can work not only with CSS sources, but also with SCSS (for eample, for inline comment). So if it import some file, we need to use parent processor parser.

[MoOx]

I see you added postcss-scss as a dev dep but I don't see any tests, did you forget to add them ?

[tinchoz49]

👍 what is the status of this feature? I preffer use postcss-import over to postcss-partial-import but for now i don't have alternative if i'm using SCSS

[MoOx]

I am just waiting for a minimal automated test to be able to merge.

[tinchoz49]

ahh ok! one more thing. @jonathantneal I think that you need to do some change with the line 367 because for example for inline comments in SCSS is necessary use postcss-scss as the parser.

maybe something like this, what do you think?

var parseFunc = (result.opts && result.opts.parser) 
  ?  result.opts.parser.parse
  :  postcss.parse
var newStyles = parseFunc(fileContent, options)

[jonathantneal]

Maybe it would be easier if we just merge the two projects, and keep the import functionality like it is in PostCSS import and make the include functionality like it is in PostCSS partial import?

[MoOx]

The idea of your plugin is just to add a prefix before the last part of the name of the file right? I don't see how you created another plugin for that and not just did a PR in the first place. This has already been discussed here #39 and the issue is still open (so PR are welcome, has always).

[CoolGoose]

+1 on this, any chance of getting this trough ? :) (helps with a lot of projects being sass based)

[MoOx]

@CoolGoose If I am correct, I think @TrySound will handle that very soon.

[MoOx]

Closed by 9c168b9, will land in master soon.