-
Notifications
You must be signed in to change notification settings - Fork 495
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
Feature Request: Additional collection functions - shuffle(), randomItems() #277
Comments
In Neo4j 3.2. there is The other ones are good ideas, also good starting point for a pull request as those are 1:1 mappings to For randomItems it probably makes more sense to have two functions instead of a boolean parameter, although as we have default values now it could just default to removeOnPick=true. |
I think I may be missing something, how do defaults work between apoc procedure calls and their paired methods? |
Since Neo4j 3.1 you can provide a defaultValue attribute on the @name annotation both for functions and procedures. There are a few examples in the 3.1 branch |
Per the recommendation on slack, I was targeting the 3.0 branch. Is it recommended to target 3.1 at this time instead? Or is it good enough to go for 3.0, and then make the boolean have a default value on 3.1, once it gets there? |
Feature request fulfilled with merge of issue #296, this is on the 3.1 branch. |
This requests some additional collection helper functions:
The text was updated successfully, but these errors were encountered: