Add support for indexing and slicing in orm.Group.nodes iterator
#2371
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sphuber
force-pushed
the
fix_2370_group_nodes_indexing_slicing
branch
from
4c0166b
to
7aeb41f
Compare
This allows one to directly get just a single or a slice of all the nodes contained within a `Group` instead of having to iterate over it to get the nodes of interest.
sphuber
force-pushed
the
fix_2370_group_nodes_indexing_slicing
branch
from
7aeb41f
to
8995084
Compare
giovannipizzi
approved these changes
Jan 8, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #2370
This allows one to directly get just a single or a slice of all the
nodes contained within a
Groupinstead of having to iterate over it toget the nodes of interest.