This repository was archived by the owner on Feb 22, 2023. It is now read-only.
[in_app_purchase] Make PurchaseDetails.status mandatory #3831
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.
While implementing the new
in_app_purchase_platform_interface
I noticed that thePurchaseDetails.status
property was migrated as a nullable field while the implementations always consider it as a mandatory (non-nullable) field.This PR corrects this mistakes and makes sure the
PurchaseDetails.status
field doesn't accept anull
value and when a new instance is created a status value has to be supplied.The original migration PR can be found here: #3781
If you had to change anything in the flutter/tests repo, include a link to the migration guide as per the breaking change policy.
Pre-launch Checklist
dart format
. See plugin_tool format)[shared_preferences]
///
).If you need help, consider asking for advice on the #hackers-new channel on Discord.