Skip to content

[Bug]: Datastore decoding unexpectedly evaluates valid values as falsy #35

@flashsturz

Description

@flashsturz

Is there an existing issue for this?

  • I have searched the existing issues

Environment

-   OS: Windows 11
-   Python: 3.10.13

What happened?

I noticed that the _decode_datastore() function unexpectedly throws an error if field values evaluate to a falsy value for some data types.

Additionally, the decoding of geoPointValue was referencing timestampValue, a simple typo.

Code Snippet

One example: Having a doubleValue field with data entry 0 leads to a TypeError.

Relevant log output

Anything else?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingtriage

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions