Changing assert to become a class#58253
Merged
nodejs-github-bot merged 16 commits intonodejs:mainfrom Aug 5, 2025
Merged
Conversation
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.
Changing assert to become a class
This PR refactors
assertfrom a method to a dedicated class. This change is motivated by the need for greater flexibility and configurability in assertion behavior.By turning
assertinto a class, we will be able to pass options that customize its behavior, such as doing specific checks, how the stack trace will look like, etc.Checklist
assertinto a class structure (old-school pattern).assertusages.cc @BridgeAR