This repository has been archived by the owner on May 13, 2023. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
Bug fix, feature, docs update, ...
What is the current behavior?
Please link any relevant issues here.
This PR adds some default values on some values.
This PR might not make sense at first glance, but the goal of this PR is to have the Flutter SDK not throw errors when the backend makes an mistake and changes the return type to nullable. Some of the values that are given default values are not very widely used. Having the app throw for parsing an object that isn't even used within the code is a pain, and this PR minimizes the effect of the mistake made on the backend.
There probably will be a few more of these PR coming!
Fixes supabase/supabase-flutter#414