Limit document updates to relevant fields #141
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
micha91
force-pushed
the
fix-update-documents
branch
from
cccdc9a to
fe8b249
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.
Currently we always send all fields we received from the server with the patch request back to the server. When a user performs changes during the document rendering, it is possible that these custom fields get overwritten by capella2polarion with outdated data. While we cannot guarantee that we don't overwrite content changes made during the rendering, it's easy to avoid overwriting data, we do not actually change in Capella2Polarion. For that reason we will only send
homePageContent,renderingLayoutsand optionallytitleandoutlineNumberingin patch requests in the future.