Skip to content
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

[MBL-1852] Update CreateBackingInput #2203

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open

[MBL-1852] Update CreateBackingInput #2203

wants to merge 5 commits into from

Conversation

scottkicks
Copy link
Contributor

📲 What

Updates the CreateBackingInput GraphQL object to support its new incremental: Bool? property.

Actual implementation will be done separately in mbl-1853.

🤔 Why

This flag will let the backend know if backers have selected the Pledge Over Time option at checkout.

🛠 How

  • Updated GraphAPI.swift via our apollo script
  • Updates the existing adapters and structs to include this new property.
  • Passes false to call points for now since implementation will be done in mbl-1853

👀 See

Tested that the new property is being sent as false in when attempting a crowdfund pledging:

Screenshot 2024-11-25 at 10 23 49 AM

✅ Acceptance criteria

  • All checkout flows work as expected
  • incremental is being added to the CreateBackingInput and is false for now.
  • Late pledge flow experiences no change and is unaware of this new property.

@nativeksr
Copy link
Collaborator

1 Warning
⚠️ Big PR

Generated by 🚫 Danger

@scottkicks scottkicks marked this pull request as ready for review November 25, 2024 16:07
@scottkicks scottkicks changed the title [MBL-1852] Update CreateBackingInput To Support New "incremental" Property [MBL-1852] Update CreateBackingInput Nov 25, 2024
Copy link
Contributor

@ifosli ifosli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! Just one typo. We will want tests at some point where pledge over time is enabled, but I trust your judgement for whether that's something that should be tested now or if it should wait.

@@ -15,6 +16,7 @@ public struct CreateBackingInput: GraphMutationInput, Encodable {

- parameter amount: The amount.
- parameter applePay: The optional ApplePayParams.
- parameter incremental: The optional Bool indicating whether pledge over time has been selected..
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: extra .

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should there be a test where incremental is true?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Definitely. My plan is to add tests when I get going on the implementation piece.

@@ -521,7 +521,8 @@ public class NoShippingPledgeViewModel: NoShippingPledgeViewModelType, NoShippin
paymentSourceId: paymentSourceId,
setupIntentClientSecret: nil,
applePayParams: applePayParams,
refTag: refTag
refTag: refTag,
incremental: false // TODO: implementation in [mbl-1853](https://kickstarter.atlassian.net/browse/MBL-1853)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like incremental is always false in this PR, is the idea to make it true sometimes in that ticket?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah! Just exposing the Boolean here. Wiring it up to the PLOT component will be done in that ticket in the inline comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants