Conversation
lafrech
force-pushed
the
lazy_components
branch
from
58ccda4 to
0d659b2
Compare
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
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.
Add lazy component registration feature.
Allows to register components only if they are actually referenced in the spec.
This can be useful for a framework that defines headers (pagination, ETag header) before knowing if the feature is actually used in the code. It avoids defining useless components. E.g. marshmallow-code/flask-smorest#236.
Security schemes are not included in the feature because they are a bit more tricky and I though it was not critical. But I wouldn't object to including them if someone is willing to implement that.