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

Improve keyword query parameters #836

Merged
merged 4 commits into from
Oct 20, 2022

Conversation

robsdedude
Copy link
Member

  • API docs: clarify precedence between keyword and dict query parameters
  • Fix: parameters of internal functions could clash with keyword parameters. E.g., db and imp_user could not be used as keyword query parameters causing a not necessarily easy to understand error message. This got fixed by merging keyword and dict parameters at the top-most level.

Backport of #835

 * API docs: clarify precedence between keyword and dict query parameters
 * Fix: parameters of internal functions could clash with keyword parameters.
   E.g., `db` and `imp_user` could not be used as keyword query parameters
   causing a not necessarily easy to understand error message.
   This got fixed by merging keyword and dict parameters at the top-most level.
Copy link
Contributor

@bigmontz bigmontz left a comment

Choose a reason for hiding this comment

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

🍎

(is there any test for checking the precedence?)

@robsdedude robsdedude merged commit 4d22919 into neo4j:4.4 Oct 20, 2022
@robsdedude robsdedude deleted the fix-keyword-query-parameters-4.4 branch October 20, 2022 06:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants