Remove current children from virtual object before initializing content metadata #418
Conversation
This file contains 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
mjgiarlo
force-pushed
the
remove_children_first_409
branch
2 times, most recently
from
a9b9f1e
to
9d2b1c6
Compare
jcoyne
requested changes
Sep 17, 2019
mjgiarlo
force-pushed
the
remove_children_first_409
branch
from
9d2b1c6
to
40aba44
Compare
…nt metadata This prevents a situation where lots of manual clean-up is required to remove old children from a parent. Fixes #409
mjgiarlo
force-pushed
the
remove_children_first_409
branch
from
40aba44
to
30a9708
Compare
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.
Fixes #409
This prevents a situation where lots of manual clean-up is required to remove old children from a parent.
Also includes:
docker-composeserviceRefreshMetadataActionspec descriptionWhy was this change made?
To satisfy the new virtual object creation requirement surfaced in #409.
Was the API documentation (openapi.json) updated?
N/A