refactor!: Remove tracking of "culprit" from Require methods #5739
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.
The string
culprit
as a marker for pointing to an issue in a stack trace has never appeared in a DHC issue, nor in DHC slack, and the last DHE slack message to use it in a mildly helpful way was more than two years ago.This patch removes the functionality from
RequirementFailure
, and also removes any overload of a method inRequire
that would allow callers to customize the depth within the stack that should be marked.Partial #188