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

Manage DuplicateComponentNameError apispec error. #138

Merged
merged 1 commit into from
Mar 21, 2019

Conversation

buxx
Copy link
Contributor

@buxx buxx commented Feb 4, 2019

Ref #137

@buxx buxx self-assigned this Feb 4, 2019
@buxx buxx requested a review from inkhey February 4, 2019 16:18
@buxx buxx force-pushed the feature/137__manage_duplicate_schema_reference branch from 41d085e to 1a26689 Compare February 25, 2019 16:22
@inkhey inkhey self-requested a review March 20, 2019 08:57
@inkhey
Copy link
Contributor

inkhey commented Mar 21, 2019

needed for #149, so we merge as there is failing tests. Last apispec version break many behaviour.

@inkhey inkhey merged commit d851263 into develop Mar 21, 2019
@buxx buxx deleted the feature/137__manage_duplicate_schema_reference branch March 21, 2019 09:18
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.

2 participants