Skip to content

Add infra config to ConfigurationContext#10199

Merged
maridematte merged 10 commits intodotnet:mainfrom
maridematte:10123
Jul 23, 2024
Merged

Add infra config to ConfigurationContext#10199
maridematte merged 10 commits intodotnet:mainfrom
maridematte:10123

Conversation

@maridematte
Copy link
Copy Markdown
Member

Fixes #10123

Changes Made

Analyzers now have access to infrastructure configuration data, which contains severity and isEnabled attributes.

@JanKrivanek
Copy link
Copy Markdown
Member

This looks great and meets original requirements.

As discussed offline - let's change CustomConfigurationData so that it has RuleId, dictionary of custom key-values, BuildAnalyzerConfiguration - that way the accessing of custome or infra config would be same (by index, or searched by RuleId)

Copy link
Copy Markdown
Member

@JanKrivanek JanKrivanek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good per the bug requirement. Though the real usage scenario (buildcheck needs to know whether a rule is enabled and what scope it should check) needs a bit of adjustment. Appology for original unclarity (I realized only after seeing the changes) - if it's easier, feel free to fix the comments here, push it, and solve effective config in separate PR

Copy link
Copy Markdown
Member

@JanKrivanek JanKrivanek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

@maridematte maridematte merged commit dd3f161 into dotnet:main Jul 23, 2024
@maridematte maridematte deleted the 10123 branch August 7, 2024 10:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Configuration - ConfigurationContext should contain infra config as well

4 participants