Skip to content

docs: Clarified laziness of create_hierarchy (#2938) #2939

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

docs: Clarified laziness of create_hierarchy (#2938) #2939

wants to merge 2 commits into from

Conversation

FabricioArendTorres
Copy link

[Description of PR]
Adjusted docstring of Group.create_hierarchy, as its lazy creation is otherwise unexpected (#2938 ).
This is more of a suggestion, as it is a rather a minor change..

TODO:

  • Add unit tests and/or doctests in docstrings
  • Add docstrings and API docs for any new/modified user-facing classes and functions
  • New/modified features documented in docs/user-guide/*.rst
  • Changes documented as a new file in changes/
  • GitHub Actions have all passed
  • Test coverage is 100% (Codecov passes)

@github-actions github-actions bot added the needs release notes Automatically applied to PRs which haven't added release notes label Mar 30, 2025
@d-v-b
Copy link
Contributor

d-v-b commented Mar 30, 2025

thanks @FabricioArendTorres

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@d-v-b d-v-b d-v-b approved these changes

Assignees
No one assigned
Labels
needs release notes Automatically applied to PRs which haven't added release notes
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@FabricioArendTorres @d-v-b