refactor(metadata): cascade resource to operation #7246
Merged
Merged
Conversation
soyuka
force-pushed
the
feat/casacde-to-op
branch
3 times, most recently
from
e4d9ddd to
e938d53
Compare
soyuka
changed the title
soyuka
force-pushed
the
feat/casacde-to-op
branch
from
e938d53 to
936e4f9
Compare
soyuka
force-pushed
the
feat/casacde-to-op
branch
from
936e4f9 to
c5c0d7e
Compare
Member
Author
|
Finally took some time to fix also the type hint on |
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.
Also related to #7213
Adds a way to update your operations without having to do it manually (only when values are null but are set on the api resource).
This code would also make a refactoring possible inside our current metadata factories.