#2043 introduce ValidationErrorNoStack class to improve error creation performance #2142
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 Pull Request introduces
ValidationErrorNoStack
, a class aimed at enhancing performance in error validation processes. Similar toValidationError
, it does not extend fromError
and avoids capturing the stack trace. This approach significantly improves efficiency, particularly for validations of large arrays.Key Features:
ValidationErrorNoStack
Class: Implements theValidationError
interface, but without stack trace capturing.disableStackTrace = false
: RetainsValidationError
, standard behavior including stack trace.disableStackTrace = true
: Switches toValidationErrorNoStack
, optimizing performance by skipping stack trace capture.Benefits:
disableStackTrace = false
ensures existing functionality is unaffected.This update provides an efficient solution for intensive validation scenarios while preserving the functionality for current users.