You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 7, 2023. It is now read-only.
Currently all columns have nullable data types. If a user has data that explicitly should not be null, this makes their code more verbose (they have to add ! everywhere) and doesn't enforce non-null input.
To support non-nullable data types, we should add a non-nullable column and/or non-nullable DataFrame.
The text was updated successfully, but these errors were encountered:
I haven't thought too hard about how to implement this yet, but I think it's going to be a bit messy and painful. Currently, we're blocking anyone who wants to update their entire app to null safety-they can't update until df supports null safety. IMO we should publish ASAP to unblock people and then add a non-nullable DataFrame later.
Currently all columns have nullable data types. If a user has data that explicitly should not be null, this makes their code more verbose (they have to add
!
everywhere) and doesn't enforce non-null input.To support non-nullable data types, we should add a non-nullable column and/or non-nullable DataFrame.
The text was updated successfully, but these errors were encountered: