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

Proper use of the "position" attribute #200

Open
arminlinder opened this issue Sep 14, 2017 · 1 comment
Open

Proper use of the "position" attribute #200

arminlinder opened this issue Sep 14, 2017 · 1 comment

Comments

@arminlinder
Copy link

arminlinder commented Sep 14, 2017

It has been asked before, but somehow the answer is not helpful: your tree library contains a "position" attribute, so the nodes of a level can be sorted. I see that some methods have optional "position" paerameters, but I could not figure out how to retrieve a whole (sub)tree (getDescendants / getDescendantsTree) with subtree nodes sorted by position.

Can you please clarify?

Thx, Armin.

@arminlinder
Copy link
Author

Did a lot of research, and found that closuretable does not seem to honor the "position" attribute when I use getDescendants, but it does so if I use getChildren.

I consider this a bug, at least an annoyance, because

  • similar functions should behave in a consistent manner
  • the returned data of getDescendants is worthless for the client, because my client tree structure will not let me assign positions out of order, e.g. i cannot insert position "4" unless positions 1,2,3 have been loaded.

Anything I can do?

Armin.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants