Make enum description reading tolerant to invalid data #1852
Conversation
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
* make reading tolerant to invalid data * don't output multiple versions, just support reading multiple
This was referenced Sep 15, 2025
This was referenced Sep 21, 2025
Merged
This was referenced Sep 28, 2025
This was referenced Oct 17, 2025
This was referenced Nov 4, 2025
This was referenced Nov 13, 2025
Merged
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.
x-enum-descriptionsas default output as it seems more widely supported, still keeping oldx-enumNameseven though seems thatx-enum-varnamesis more supportedPayPal API description have objects in array instead of string, we're also getting reports of unwanted output (#1853)
fixes #1853
/cc @lekhmanrus