Re:Rome: A Linter for JavaScript and TypeScript
by rattray on Sunday August 09, 2020 @08:16AM
(#24099096)
Very interesting! Thanks for clarifying.
I've also done some work on Prettier in the past, so I'm curious about some details there too.
1. Do you plan to build a wadler-based formatter, similar to prettier? Will it be as opinionated as prettier, or based on a pluggable architecture? (I'll admit that I have yet to conceive of a viable way to make the latter work well).
2. Have you considered (or already built) an incremental parsing server for tools like the formatter? For example, when I add a statement at the bottom of the document, will it reparse the whole document, or be smart enough to notice that a change has been made that can use cached results for most of the AST? (I'm not sure if this is feasible for JS, especially for parsers that require line/col info).
In any case, I'll be following your progress with great interest!
I've also done some work on Prettier in the past, so I'm curious about some details there too.
1. Do you plan to build a wadler-based formatter, similar to prettier? Will it be as opinionated as prettier, or based on a pluggable architecture? (I'll admit that I have yet to conceive of a viable way to make the latter work well).
2. Have you considered (or already built) an incremental parsing server for tools like the formatter? For example, when I add a statement at the bottom of the document, will it reparse the whole document, or be smart enough to notice that a change has been made that can use cached results for most of the AST? (I'm not sure if this is feasible for JS, especially for parsers that require line/col info).
In any case, I'll be following your progress with great interest!