Skip to content

buildTree is dependent on the metadata key order #6330

@gbalint

Description

@gbalint

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:

Image

That results in a different path tree then for the following one (which has proper order accrding to the hierarchy):

Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions