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

Make sorting in climb() and prune() configurable #271

Merged
merged 3 commits into from
Jan 7, 2025
Merged

Conversation

psss
Copy link
Collaborator

@psss psss commented Jan 6, 2025

Allow users to disable sorting by node names and preserve the order in which child nodes where inserted into the tree.

Checklist

  • implement the feature
  • write the documentation
  • extend the test coverage
  • mention the version
  • include a release note

Copy link
Contributor

@LecrisUT LecrisUT left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When sort=False it is a bit confusing what order are child nodes created in w.r.t. scatter feature.

docs/features.rst Outdated Show resolved Hide resolved
psss added 3 commits January 7, 2025 13:39
Allow users to disable sorting by node names and preserve the
order in which child nodes where inserted into the tree.
@psss psss force-pushed the optional-prune-sort branch from c89892c to 21a2964 Compare January 7, 2025 12:40
@psss psss self-assigned this Jan 7, 2025
@psss psss merged commit baaccc9 into main Jan 7, 2025
12 of 13 checks passed
@psss psss deleted the optional-prune-sort branch January 7, 2025 13:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants