Skip to content

Raise hydration errors on value access #759

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

Merged
merged 3 commits into from
Jul 18, 2022

Conversation

robsdedude
Copy link
Member

This has its limitations, thought. If a user returns for instance a list with one invalid value in it, the Record would throw on trying to access the list. So the user still could't salvage the other list entries. I don't think, however, there's a Pythonic way to cater for this use-case.

@robsdedude robsdedude force-pushed the broken-hydration-object branch 2 times, most recently from a14904c to fab921f Compare July 13, 2022 14:55
@robsdedude robsdedude force-pushed the broken-hydration-object branch from fab921f to b514f97 Compare July 13, 2022 15:05
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.

🤖

@robsdedude robsdedude merged commit a41f827 into neo4j:5.0 Jul 18, 2022
@robsdedude robsdedude deleted the broken-hydration-object branch July 18, 2022 07:20
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