Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(initialisation): Make sure to select valid IAnalyzerResult from Buildalyzer #1900

Merged
merged 2 commits into from
Feb 11, 2022

Conversation

0xced
Copy link
Contributor

@0xced 0xced commented Feb 10, 2022

Fixes #1899

@rouke-broersma rouke-broersma changed the title Make sure to select the right IAnalyzerResult from Buildalyzer fix(initialisation): Make sure to select valid IAnalyzerResult from Buildalyzer Feb 11, 2022
@rouke-broersma rouke-broersma enabled auto-merge (squash) February 11, 2022 07:49
@rouke-broersma rouke-broersma merged commit da2cd52 into stryker-mutator:master Feb 11, 2022
@0xced 0xced deleted the analyzer-result branch February 11, 2022 08:51
0xced added a commit to 0xced/stryker-net that referenced this pull request Dec 30, 2023
Just like stryker-mutator#1900 but for the InputFileResolver.

This was not an issue until phmonte/Buildalyzer#198 was reverted in phmonte/Buildalyzer@8e85a15 for the Buildalyzer 6.0.1 release. Before this change in Buildalyzer, the empty target framework was sorted last but since v6.0.1 it's sorted first instead.

Also, improve the NotSupportedException message when the language is undefined because `System.NotSupportedException: Specified method is not supported` is a terrible message.
rouke-broersma pushed a commit that referenced this pull request Dec 30, 2023
Make sure to select valid IAnalyzerResult from Buildalyzer

Just like #1900 but for the InputFileResolver.

This was not an issue until phmonte/Buildalyzer#198 was reverted in phmonte/Buildalyzer@8e85a15 for the Buildalyzer 6.0.1 release. Before this change in Buildalyzer, the empty target framework was sorted last but since v6.0.1 it's sorted first instead.

Also, improve the NotSupportedException message when the language is undefined because `System.NotSupportedException: Specified method is not supported` is a terrible message.
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.

Breaks when using reproducible builds
2 participants