close #670; fix: replace <> with _ in generic object names #671
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
sunli829
force-pushed
the
master
branch
4 times, most recently
from
0c16a9b
to
f6bec88
Compare
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.
Description
This PR addresses the issue raised in #670, where the use of generics in object names was causing non-compliance with OpenAPI specifications.
Changes:
Replaced occurrences of < and > with underscores (_) in generic object names to ensure compatibility.
Updated relevant tests to reflect this change.
This fix ensures that our generated output aligns with RFC3986-compliant standards and avoids potential conflicts with other systems or tools expecting compliant URIs.
Please review the changes and let me know if further adjustments are needed.