[WIP] [OpenAPI]: Blueprint inheritance#302
Draft
Abishekcs wants to merge 1 commit into
Draft
Conversation
- When a blueprint subclasses another blueprint (not Blueprinter::Base itself), parse the parent class and merge its fields into the child's schema. - A child re-declaring a field with a different `name:` wins over the parent's original field declaration.
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
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.
closes #290
What this PR does?
Add support for blueprint inheritance. Child blueprints now inherit fields from parent blueprints. A child re-declaring a field with a different
name:takes priority over the parent's declaration.Example Code
data_mining_base.rbdata_mining.rbOpenAPI response output for # @response DataMiningScreenRecording
Before
After