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-1690] Crash When Selecting 'Edit Reward' Option In Manage Pledge Flow #2145

Merged
merged 5 commits into from
Sep 5, 2024

Conversation

scottkicks
Copy link
Contributor

📲 What

Uses the filtered rewards by location list to scroll to the selected reward via the 'Edit Reward' option in our Manage Pledge flow.

🤔 Why

this is the list the app uses when in our No Shipping At Checkout Flow.

🛠 How

Adds the filteredByLocationRewards list to the scrollToBackedRewardIndexPath signal and chooses the right list to use based on if that list is empty or not.

👀 See

Simulator Screen Recording - iPhone 15 Pro 17 5 - 2024-09-03 at 14 31 03

✅ Acceptance criteria

  • Backers can edit their selected reward when the No Shipping At Checkout feature flag is on
  • Backers can edit their selected reward when the No Shipping At Checkout feature flag is off

@scottkicks scottkicks marked this pull request as ready for review September 5, 2024 15:38
@scottkicks scottkicks requested review from a team, jlplks, ifosli and stevestreza-ksr and removed request for a team and jlplks September 5, 2024 15:38
@scottkicks scottkicks merged commit 427b313 into main Sep 5, 2024
5 checks passed
@scottkicks scottkicks deleted the scott/mbl-1690/edit-reward-crash branch September 5, 2024 19:00
ifosli pushed a commit that referenced this pull request Sep 5, 2024
… Flow (#2145)

* add a test for when the 'update pledge' option is not an option when the feature flag is enabled

* scroll to index path should be based on rewards filtered by location
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