Add Declarative Configuration for Ignoring Apex Classes in Stack Traces#908
Open
JMercie wants to merge 2 commits intojongpie:mainfrom
Open
Conversation
…k traces. This allows admins to globally configure Apex classes to be filtered from stack traces without requiring developer code changes, addressing issue jongpie#890.
…pulate a value for the mdt record.
This file contains hidden or 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
1 participant
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.
Issue Reference: #890
Solution
Implemented a declarative approach that allows admins to configure Apex classes to ignore globally through Custom Metadata Types, without requiring any code changes.
Changes