reimplemented litmoon - #217
Conversation
nonchip
commented
Sep 28, 2015
whoops, thanks travis, missed something there, i'll fix |
nonchip
commented
Sep 28, 2015
done. |
nonchip
commented
Oct 6, 2015
@leafo ping? |
leafo
commented
Oct 6, 2015
Haven't had a chance to review yet, this is a much bigger change. |
nonchip
commented
Nov 24, 2015
will this be reviewed anytime soon? most of the changes are autocompiled lua anyway, busted passes (ofc i added a test for litmoon), and there's at least 2 projects already using it, so imho it'd be worth the time… |
nonchip
commented
Mar 9, 2016
seriously, i don't see how this "bigger change" (consisting of some few adjustments in about 5 files and running |
| concat moonpaths, ";" | ||
| to_lua = (text, options={}) -> | ||
| to_lua = (text, options={}, litmoon=false) -> |
There was a problem hiding this comment.
I don't think adding another argument specific to litmoon is a good change to this interface. (If we add more formats are we supposed to keep adding new arguments?) Any reason you didn't re-purpose options?
nonchip
commented
Apr 14, 2016
you're right, i'll try to reimplement this using the options tables instead. did kinda mistake them for being strictly structured stuff i'd better not touch… |
there you go. using lpeg this time, because what the hell did I hack there before :P
tried to break as little as possible, and went with a factory approach where I always default to litmoon=false and generate the default functions in case someone was depending on them somewhere else.
general idea:
also the mechanism for filtering is actually pretty simple: extend
moonscript.parser.literals.EmptyLineon demand (using above factory design) and redefineLineas(CheckIndent * Statement + Space * #Stop) + EmptyLine