Klaus Meinhardt
Klaus Meinhardt
To avoid too much breakage for existing configs, if there's no `wotan.config.`, but a `.wotanrc.`, use that and convert it to the new config format (and also search for `.fimbullinter.yaml`)....
Some more thoughts: * moving CLI defaults to `wotan.config.` might not be necessary yet. That could be done later if needed. * making the config responsible for loading additional scripts...
Regarding automatic prefixing: this is probably not the best option. The full-compat (`@fimbul/valtyr`) configs should not prefix anything. Instead configs should be able to provide declarations in the default namespace....
Some more thoughts: * mixing full-compat configs (including disable comments, ..) may be very confusing. in the long run there should only be a single Wotan config that contains soft-compat...
reminder to self: needs to handle union signatures and higher order function/constructor type inference
This is kinda working as intended. You could use the type parameter within the function body to ensure type safety or infer the return type: ```ts function a(param: T) {...
Affected rules: * prefer-object-spread * prefer-const * prefer-for-of And probably every fixer that could leave a trailing comma behind.
Another special case in property initializer regarding parameter properties: ```ts //@target: ESnext // @useDefineForClassFields: true class C { prop = this.obj; // error on 'obj' constructor(private obj: any) {} }...
no-useless-declare can add a check to disallow `declare prop: T;` in an ambient class.
TBD: add an option to limit/disable concurrency?