Skip to content

Fixing start_at, end_at, equal_to queries to accept False values#96

Merged
hiranya911 merged 2 commits into
masterfrom
hkj-fix-query
Nov 30, 2017
Merged

Fixing start_at, end_at, equal_to queries to accept False values#96
hiranya911 merged 2 commits into
masterfrom
hkj-fix-query

Conversation

@hiranya911
Copy link
Copy Markdown
Contributor

start_at(), end_at() and equal_to() method in the Query class currently does not accept False as a valid argument (along with a bunch of other false values such as empty string and empty dict). This PR relaxes the argument checks so these values are supported.

Resolves #88. Related to #89.

Copy link
Copy Markdown
Contributor

@avishalom avishalom left a comment

Choose a reason for hiding this comment

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

Delete the "empty" from the doc string

Comment thread firebase_admin/db.py Outdated
@@ -444,8 +444,8 @@ def start_at(self, start):
Raises:
ValueError: If the value is empty or None.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

If empty is ok, amend comments here and below

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Done. Good catch.

@hiranya911 hiranya911 assigned hiranya911 and unassigned avishalom Nov 29, 2017
@hiranya911 hiranya911 assigned avishalom and unassigned hiranya911 Nov 29, 2017
@avishalom avishalom assigned hiranya911 and unassigned avishalom Nov 30, 2017
@hiranya911 hiranya911 merged commit 11f70f0 into master Nov 30, 2017
@hiranya911 hiranya911 deleted the hkj-fix-query branch November 30, 2017 18:33
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