We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
buildTree can results in different element path trees for the same metadata maps with different key orders.
See e.g. the following metadata maps:
This one has the card/ descendants split into two different sections of the key array:
card/
That results in a different path tree then for the following one (which has proper order accrding to the hierarchy):
The text was updated successfully, but these errors were encountered:
No branches or pull requests
buildTree can results in different element path trees for the same metadata maps with different key orders.
See e.g. the following metadata maps:
This one has the
card/
descendants split into two different sections of the key array:That results in a different path tree then for the following one (which has proper order accrding to the hierarchy):
The text was updated successfully, but these errors were encountered: