Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Normalize Swagger definitions before resolving a subtree #1274

Merged

Conversation

shockey
Copy link
Contributor

@shockey shockey commented Apr 4, 2018

This PR:

  • normalizes subtree data before attempting to resolve it, to solve the problem of path parameters outside of an operation's resolution discriminator being added to the operation in an unresolved form
  • adds a top-level $$normalized marker to resolved definitions, in order to make the subtree resolver idempotent when its previous result is passed in as an input.

Fixes swagger-api/swagger-ui#4327.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Empty parameter field is rendered when defined in Path Item Object's parameters
1 participant