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

[NT-226] Cancel backing navigation workflow #860

Merged
merged 9 commits into from
Sep 30, 2019
Merged

Conversation

ifbarrera
Copy link
Contributor

@ifbarrera ifbarrera commented Sep 30, 2019

📲 What

Creates CancelPledgeViewController along with CancelPledgeViewModel and test setup. Configures ManagePledgeViewController to push this new VC onto the stack when Cancel pledge is selected from the action sheet menu.

🤔 Why

Setup for cancel pledge.

👀 See

Ou6VVgKR9j

♿️ Accessibility

  • Tap targets use minimum of 44x44 pts dimensions
  • Works with VoiceOver
  • Supports Dynamic Type

✅ Acceptance criteria

  • With the Native Checkout and Native Pledge Screen feature flags turned ON, navigate to a backed project. Tap the menu button on the top right. Select "Cancel pledge" - you should be taken to a new screen with the title set to "Cancel pledge". The back button should appear on the top left.

@@ -32,8 +32,6 @@ extension RewardPledgeNavigationController: UINavigationControllerDelegate {
case (.pop, is PledgeViewController, is RewardPledgeTransitionAnimatorDelegate):
return RewardPledgePopTransitionAnimator()
default:
// We're not performing any custom transition, bring back the standard divider line
self.navigationBar.shadowImage = nil
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Removed this line in favor of keeping the shadow for all VCs managed by RewardPledgeNavigationController. This will cause some funkiness with colors in the deprecated pledge VC and possibly the Thanks page, but I think we can easily fix those during a design pass - ideally we can get to a place where there's visual consistency between all the VCs in the checkout flow.

Copy link
Contributor

Choose a reason for hiding this comment

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

Can you describe what funkiness do you have in mind? 😄

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I believe what might happen is the line won't come back in the Thanks VC after checkout. What I think we should do is do a light colors pass on the Thanks screen to make it visually consistent with the other screens in the new checkout flow.

Copy link
Contributor

@cdolm92 cdolm92 left a comment

Choose a reason for hiding this comment

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

Left a comment, this is G2G after that's addressed. Awesome work!! 🎉🛳

public protocol CancelPledgeViewModelInputs {
func configure(with project: Project, backing: Backing)
func viewDidLoad()
}
Copy link
Contributor

Choose a reason for hiding this comment

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

The order here is different. Inputs should go before the Outputs

Copy link
Contributor

@dusi dusi 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

@@ -32,8 +32,6 @@ extension RewardPledgeNavigationController: UINavigationControllerDelegate {
case (.pop, is PledgeViewController, is RewardPledgeTransitionAnimatorDelegate):
return RewardPledgePopTransitionAnimator()
default:
// We're not performing any custom transition, bring back the standard divider line
self.navigationBar.shadowImage = nil
Copy link
Contributor

Choose a reason for hiding this comment

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

Can you describe what funkiness do you have in mind? 😄

@ifbarrera ifbarrera merged commit 428bd67 into master Sep 30, 2019
@ifbarrera ifbarrera deleted the cancel-backing-setup branch September 30, 2019 21:16
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.

3 participants