Avoiding errors on as-yet-undefined syntax

[TonyGravagno]

I was going to post this suggestion here but I brain dumped in this issue.

Might this be a way to allow the plugin to process whatever it can, and ignore whatever it doesn't recognize?

After the joy of finding this plugin (and the enhancements over prior tooling) I was saddened that any unrecognized syntax would cause a termination of the parsing process, resulting in a loss of whatever could be processed.

[nene]

Yeah, I think this sort of approach should work and should be pretty simple to implement.

It should be enabled with some flag though, so it could be toggled on/off.

[nene]

I've now finally implemented this suggestion. One can now use the acceptUnsupportedGrammar option (or sqlAcceptUnsupportedGrammar in the prettier plugin) to enable it.