Skip to content
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

Differentiator does not always put excluded objects underneath the specialised objects of the same nodeId #565

Open
VeraPrinsen opened this issue Jan 31, 2024 · 0 comments

Comments

@VeraPrinsen
Copy link
Collaborator

Example:
parentArchetype.txt
childArchetype.txt
grandChild_before_specialising_and_excluding_id7.txt

At our end, id7 is specialised and excluded and the following archetypes are used as input for the Differentiator().differentiate(flatChild, flatParent):
flattenedChild.txt
flattenedParent.txt

Output of the Differentiator().differentiate():
differentiatedChild.txt

Now the ELEMENT[id5.1] and ELEMENT[id7] are excluded before the elements are specialised, resulting in a warning: Object with node id 7 should be specialized before excluding the parent node. I also heard that this warning will in a future update result in a validation error instead.

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

No branches or pull requests

1 participant