fix: error handling in guardian handlers for forbidden depreated feature #1086
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.
🔧 Changes
This pull request introduces error handling improvements across multiple handlers in the
auth0
toolset to handle forbidden feature errors and enhance robustness. The changes include adding a new utility functionisForbiddenFeatureError
, updating thegetType
methods of several handlers, and improving logging for better debugging.Error Handling Enhancements
New Utility Function: Added
isForbiddenFeatureError
identifying forbidden feature errors and log warnings.Imports Standardization:
isForbiddenFeatureError
imports to multiple handler files for consistent error handling:guardianFactorProviders
guardianFactorTemplates
guardianFactors
guardianPhoneFactorMessageTypes
guardianPhoneFactorSelectedProvider
📚 References
🔬 Testing
Test pass ✅
📝 Checklist