Loading workspace insights... Statistics interval
7 days30 daysLatest CI Pipeline Executions
ce7c868c fix(linter): insert framework configs before baseConfig in flat config
In flat config, later array entries override earlier ones. Framework
generators appended predefined configs (flat/react, flat/angular, etc.)
after baseConfig, causing framework rules to override user root rules.
Implement the checkBaseConfig option in addBlockToFlatConfigExport to
find the ...baseConfig spread element and insert before it. Framework
generators pass checkBaseConfig: true so their configs are placed before
baseConfig, giving user root config higher priority. When baseConfig
is not found (root standalone projects), falls back to appending.
Also scope the parser/plugins config entries in flat/typescript,
flat/javascript, and flat/angular to their respective file types.
Previously these entries had no files restriction, applying the
TypeScript parser to all files globally (including .html, .json, etc.).
This completes the scoping fix started in PR #28381 which only scoped
the rules/extends but missed the parser entries.
Refactor addPredefinedConfigToFlatLintConfig to use an options object
instead of positional params for optional arguments. ce7c868c fix(linter): insert framework configs before baseConfig in flat config
In flat config, later array entries override earlier ones. Framework
generators appended predefined configs (flat/react, flat/angular, etc.)
after baseConfig, causing framework rules to override user root rules.
Implement the checkBaseConfig option in addBlockToFlatConfigExport to
find the ...baseConfig spread element and insert before it. Framework
generators pass checkBaseConfig: true so their configs are placed before
baseConfig, giving user root config higher priority. When baseConfig
is not found (root standalone projects), falls back to appending.
Also scope the parser/plugins config entries in flat/typescript,
flat/javascript, and flat/angular to their respective file types.
Previously these entries had no files restriction, applying the
TypeScript parser to all files globally (including .html, .json, etc.).
This completes the scoping fix started in PR #28381 which only scoped
the rules/extends but missed the parser entries.
Refactor addPredefinedConfigToFlatLintConfig to use an options object
instead of positional params for optional arguments. ce7c868c fix(linter): insert framework configs before baseConfig in flat config
In flat config, later array entries override earlier ones. Framework
generators appended predefined configs (flat/react, flat/angular, etc.)
after baseConfig, causing framework rules to override user root rules.
Implement the checkBaseConfig option in addBlockToFlatConfigExport to
find the ...baseConfig spread element and insert before it. Framework
generators pass checkBaseConfig: true so their configs are placed before
baseConfig, giving user root config higher priority. When baseConfig
is not found (root standalone projects), falls back to appending.
Also scope the parser/plugins config entries in flat/typescript,
flat/javascript, and flat/angular to their respective file types.
Previously these entries had no files restriction, applying the
TypeScript parser to all files globally (including .html, .json, etc.).
This completes the scoping fix started in PR #28381 which only scoped
the rules/extends but missed the parser entries.
Refactor addPredefinedConfigToFlatLintConfig to use an options object
instead of positional params for optional arguments. 69412e91 fix(linter): insert framework configs before baseConfig in flat config
In flat config, later array entries override earlier ones. Framework
generators appended predefined configs (flat/react, flat/angular, etc.)
after baseConfig, causing framework rules to override user root rules.
Implement the checkBaseConfig option in addBlockToFlatConfigExport to
find the ...baseConfig spread element and insert before it. Framework
generators pass checkBaseConfig: true so their configs are placed before
baseConfig, giving user root config higher priority. When baseConfig
is not found (root standalone projects), falls back to appending.
Also scope the parser/plugins config entries in flat/typescript,
flat/javascript, and flat/angular to their respective file types.
Previously these entries had no files restriction, applying the
TypeScript parser to all files globally (including .html, .json, etc.).
This completes the scoping fix started in PR #28381 which only scoped
the rules/extends but missed the parser entries.
Refactor addPredefinedConfigToFlatLintConfig to use an options object
instead of positional params for optional arguments. 69412e91 fix(linter): insert framework configs before baseConfig in flat config
In flat config, later array entries override earlier ones. Framework
generators appended predefined configs (flat/react, flat/angular, etc.)
after baseConfig, causing framework rules to override user root rules.
Implement the checkBaseConfig option in addBlockToFlatConfigExport to
find the ...baseConfig spread element and insert before it. Framework
generators pass checkBaseConfig: true so their configs are placed before
baseConfig, giving user root config higher priority. When baseConfig
is not found (root standalone projects), falls back to appending.
Also scope the parser/plugins config entries in flat/typescript,
flat/javascript, and flat/angular to their respective file types.
Previously these entries had no files restriction, applying the
TypeScript parser to all files globally (including .html, .json, etc.).
This completes the scoping fix started in PR #28381 which only scoped
the rules/extends but missed the parser entries.
Refactor addPredefinedConfigToFlatLintConfig to use an options object
instead of positional params for optional arguments.