While the new 'safely safe changes' option is nice, it might be undesirable for a TypeScript project that has looser configuration options & might emit diagnostics for reasons unrelated to the current file(s) being modified. Add a flag to override this behavior (but keep it as the default)
While the new 'safely safe changes' option is nice, it might be undesirable for a TypeScript project that has looser configuration options & might emit diagnostics for reasons unrelated to the current file(s) being modified. Add a flag to override this behavior (but keep it as the default)