Refactoring: consumeA<Function|...>(...) should be <Func|...>.consumeFrom(...) about parse-css HOT 2 CLOSED

I'm fine with adding this kind of API, but the reason I have the functions named as they are is to just match the spec's algorithm names. There's also some functions that don't map directly to a type (like consumeAListOfDeclarations.

from parse-css.

Yes, I did see the consume functions for which no type existed, and I was planning to create fake ones for them.

I'm fine with keeping the old function names as aliases, the only intent is to make it easier to understand what's going; for instance it's hard to know right now that the "value" of an AtRule is a SimpleBlock; if the parsing function was closer to the declaration help understand the intent better, I think.

I'll work on that sometime this week, maybe Wednesday.

from parse-css.