Fixes issue where register_api isn't idempotent #230
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.
In a situation where we may instantiate multiple apps that register the same blueprint, this change updates register_api to always update the APIBlueprint's instance variables to the same values no matter how many times it is invoked.
Checklist:
pytest tests
and no failed.ruff check flask_openapi3 tests examples
and no failed.mypy flask_openapi3
and no failed.mkdocs serve
and no failed.For the fix here, I opted to update an additional field in the api rather than not updating the API because I thought that it would be helpful to have the proper updated
api.paths
field. I'm open to other approaches as well!