ezno
ezno copied to clipboard
More configuration and per file options/configuration
Currently there exists TypeCheckOptions
, which offers some very basic configuration that isn't really implemented.
Thinking further about configuring the checker for certain things. I think it needs to be more granular than a bunch of bool
s that apply to ever piece of code in the project.
Maybe one package allows console + 2
etc. Maybe another needs to parse comments for JSDoc. Things such as calling new (function x() {})
might be disallowed for user function
s (which could provide speedups for the compiler etc).
Somethings to think about:
- Figuring out where speedups can occur from configuration
- Figuring out what is type checking and what is more linting (allowed in the runtime, but discouraged)
- I think there a very few that actually come under type checking and most are linting, which should not be added to
ezno-checker
, as it's role is just a checker (based on runtime)
- I think there a very few that actually come under type checking and most are linting, which should not be added to
- Figuring out what TSC configuration is and how to correspond