[ℹ️] NT-849 Adding id field to checkout model #735
Merged
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
Adding
id
field toCheckout
model🤔 Why
It will be used in the
Back a project
tracking events.🛠 How
checkout.id
field toCreateBacking
andUpdateBacking
mutations.id
field toCheckout
model.ApolloClientType.createBacking
andupdateBacking
now return aCheckout
.CheckoutFactory
to easily return mockCheckout
objects for tests.PledgeFragmentViewModel
andPledgeFragmentViewModelTest
.👀 See
Under the hood changes only.
📋 QA
Backing or updating a pledge should behave the same.
Story 📖
NT-849