added comma separated imports

[JosephLing]

Added comma seperated imports and 2 unit tests for it :)

The only thing missing maybe is that haven't worked out how to change the span to pick up on the change in location of the error. For example:

Error: Expected string.
  |
1 | @import 'dog', 1;
  |         ^
  |
./..\mole\_css\main.scss:1:9

[pickfire]

This part seemed duplicated, could split it into a function.

[JosephLing]

Yes the code for pattern matching/parsing a single import is duplicated but it is only done duplicated once. And as the code won't be needed to be reused anywhere else I am going to keep it simple and not split it up. However can do if anyone wants it split up :)

[connorskees]

Thanks for working on this!

With regard to span information, that is currently a major failing of grass. For simplicity, spans are currently untested. This is not currently a big deal, and it should be resolved during work on adding support for source maps. You are free to ignore them for now (unless they are particularly egregious).

It would be nice to have tests for a heterogeneous group of imports -- that is, a comma separated import containing both plain CSS and Sass imports.

A test for the output of trailing commas, e.g. @import "foo.css", "bar.css",,,; would also be useful.

[connorskees]

Thank you! Everything looks good to me.

Ideally in the future we will use a different parser for imports (rather than relying on value parsing, but still using try_parse_url), but for now this works good enough for what should be most realistic use cases.

[JosephLing]

Sweet, what would be a good area of the code to look into learning how to do that? (using a different parser than value parsing)