I.e. add ability to manipulate the jison-helpers-lib::checkActionBlock() behaviour.
Currently all code blocks MUST pass JavaScript validation performed by that API through using esprima/recast, but several examples exist which showcase grammars with admittedly non-working, non-compiling code and we don't want to bother about that.
Food For Thought
The other, more sensible?, use case is when you create parsers/lexers and code your action blocks and/or other code sections in there in another language that compiles to JavaScript, say TypeScript. Currently jison does NOT support that mode of usage; it MAY be useful to provide a pre-compile/pre-process plugin interface for said API so that a user-determined and user-specified toolchain CAN be applied to every chunk of code and thus help produce a validated parser/lexer instance or sourcecode. 🎉
I.e. add ability to manipulate the
jison-helpers-lib::checkActionBlock()
behaviour.Currently all code blocks MUST pass JavaScript validation performed by that API through using esprima/recast, but several examples exist which showcase grammars with admittedly non-working, non-compiling code and we don't want to bother about that.
Food For Thought
The other, more sensible?, use case is when you create parsers/lexers and code your action blocks and/or other code sections in there in another language that compiles to JavaScript, say TypeScript. Currently jison does NOT support that mode of usage; it MAY be useful to provide a pre-compile/pre-process plugin interface for said API so that a user-determined and user-specified toolchain CAN be applied to every chunk of code and thus help produce a validated parser/lexer instance or sourcecode. 🎉