Move Ensure and ExtensionRoots to Platform.Assertions library #79
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.
Summary
This PR implements the decision from issue #68 to move assertion functionality (
Ensureand related extension roots) fromPlatform.Exceptionsto a newPlatform.Assertionslibrary.Key changes:
Platform.AssertionslibraryEnsure.cs,EnsureExtensions.csandExtensionRootsclasses toPlatform.AssertionsPlatform.ExceptionstoPlatform.AssertionsPlatform.Assertions.TestsPlatform.Exceptionsto referencePlatform.AssertionsTest Plan
Technical Details
Assertion functionality is based on predicates (conditions), while exception throwing is unconditional. This separation follows the principle that:
Platform.AssertionsPlatform.ExceptionsThe move maintains backward compatibility through a project reference from Platform.Exceptions to Platform.Assertions.
🤖 Generated with Claude Code
Resolves #68