Add analyzer for public API and revert an unintentional breaking change from 2.3 #264
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This uses analyzers from https://github.com/dotnet/roslyn-analyzers/tree/master/src/PublicApiAnalyzers to ensure the public API of this library remains stable. It should also help avoid adding new API that will have backwards compat issues going forward.
This also reverts an unintentional API break -- the public ctor for PhysicalConsole.
For contributors
When adding new API, I recommend using Visual Studio 2019. The code fixes will recommend adding the appropriate content to PublicApi.Unshipped.txt.