Move all BuildCheck related code to experimental namespace #10114
Conversation
This file contains 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.
Fixes #10099
Context
Currently some of the BuildCheck classes are delivered in Experimental napespace but Infrastructure for example (which is internal only) not.
However in order to be consistent with the exposing api public or developing api for internal use let's move all of them under experimental for the development period of time.
Changes Made
Move BuildCheck related code to Experimental namespace
Testing
All existing tests should pass
Notes
The PR moves not only Infrastructure related code but Logging and Acquisition and related to it as well.