Skip to content

Explain some caveats in change tracking #1798

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 12 commits into
base: main
Choose a base branch
from

Conversation

vmikhailenko
Copy link
Contributor

Change tracking documentation is extended to attempt to clear two things that cause confusion between stakeholders:

  • the element-defined identifier should not be used for compositions as it does very little sense for them.
  • the stakeholders need to ensure that change-tracked entities are updated using deep updates from the root of the document (entity with compositions). Notably, the changes are not linked to their expected parents and this causes confusion.

@vmikhailenko vmikhailenko requested a review from beckermarc April 29, 2025 11:24
@vmikhailenko vmikhailenko requested a review from beckermarc May 5, 2025 07:42
@vmikhailenko vmikhailenko requested a review from beckermarc May 5, 2025 10:58
@vmikhailenko vmikhailenko requested a review from beckermarc May 9, 2025 15:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants