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
feat: improve type information #176
feat: improve type information #176
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@HemangChothani Please rebase / retarget your changes against the current master
branch. The v2-staging
branch is no longer active (@crwilcox force-pushed it to master
last week).
… into firestore_improve_type
… into firestore_improve_type
Blocked on #188. |
… into firestore_improve_type
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@crwilcox Please check my comments here: my typing-fu may not be strong enough.
… into firestore_improve_type
…ython-firestore into firestore_improve_type
@tseaver I think your comments are generally correct. Not sure my stance on optional vs union with none, but they should be ~equivalent. |
… into firestore_improve_type
… into firestore_improve_type
… into firestore_improve_type
@tseaver PTAL |
@tseaver I think your suggestions make sense. Unfortunately they are out of date so I cannot auto-apply I think Union with None is clearer what is going on with the return. |
Fixes #139