Fix: Handle nested structures in castInput function #123
Conversation
This file contains 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
- Updated the `castInput` function to properly handle nested structures such as dictionaries and lists in JWT payloads. - Added recursive processing for dictionaries and lists to ensure all nested values are correctly cast. - Improved handling of string inputs, including JSON parsing, boolean conversion, and fallback cases. - Fixed a bug where lists in the payload caused a `TypeError` due to improper type handling in the previous implementation. This change addresses issues encountered when processing complex JWT payloads with deeply nested structures, such as Salesforce-style claims. The updated function ensures the tool is more robust and capable of handling various input types without errors.
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.
castInputfunction to properly handle nested structures such as dictionaries and lists in JWT payloads.TypeErrordue to improper type handling in the previous implementation.This change addresses issues encountered when processing complex JWT payloads with deeply nested structures, such as Salesforce-style claims. The updated function ensures the tool is more robust and capable of handling various input types without errors.