8000 NT-1585:Reward with starting time restriction not started yet. by Arkariang · Pull Request #1009 · kickstarter/android-oss · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

NT-1585:Reward with starting time restriction not started yet. #1009

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

Conversation

Arkariang
Copy link
Contributor

📲 What

Several bugs have occurred that allow a backer to back for rewards outside of the time frame that creators set for them. We solved this for when a reward has expired (is past the end date and time the creator set), but there is an additional scenario we missed which is when a reward should not yet be available (because it is before the start date and time the creator set). Currently, backers are able to see these rewards in the carousel and back for them.

🛠 How

  • Fetch startsAt field for GraphQL and V1 APIs.
  • Filter out from the rewards list on RewardsFragmentViewModel the ones that hasn't started yet
  • Added new method on RewardsUtils to check if a Reward is limited on staring time
  • Added new method on RewardsUtils to check if a Reward has started or not

👀 See

  • Before 🐛 you could see the not started reward on the rewards carousel
    reward_not_started

  • Now the rewards not started yet not longer showing in the rewards carousel
    filtered_out_reward_not_starter

| | |

📋 QA

  1. Go to Bots Up project (on staging)
  2. See reward tier "Reward that hasn't started yet" (start date of October 8 at 12 am).
    Expected: this tier is not visible because it is not yet October 8 at 12 am.

Story 📖

NT-1585

@Arkariang Arkariang marked this pull request as ready for review October 7, 2020 17:46
@Arkariang Arkariang self-assigned this Oct 7, 2020
…#1010)

* - AddOn new pledge or updating pledge but not previously backed follow time restrictions
- If updating pledge for previously backed addOns do not follow any restriction and let the user modify their selection.

* - Fiter out not valid time range addOns in case is new pledge or selecting another reward
- If backed addOn no longer valid in time range and selecting same reward allow modifications
@Arkariang Arkariang merged commit ea99fe9 into feature/NT-1382-Backing-Add-Ons Oct 9, 2020
@Arkariang Arkariang deleted the imartin/NT-1585-not-available-yet-reward branch October 9, 2020 15:08
Arkariang added a commit that referenced this pull request Oct 15, 2020
* NT-1231 Creator Perspective query + View your pledge updated (#895)
* NT-1141: Refactor existing queries (#897)
* NT-1294: RecyclerView structure for reward & Add-ons (#896)
* NT-1222:Retrieve Add-ons data from Graph (#899)
* NT- 1290: Add-ons UI in BackingFragment (#900)
* NT-1171: Manage Pledge View Backing Info updates (#902)
* NT-1290: Add-ons UI(with real data from staging) (#905)
* NT-1326: Pledge header ui just for rewards (#906)
* NT-1327: Header animation (#911)
* NT-1171: (Fixed) Manage Pledge View Backing Info updates (#912)
* NT-1326 : Add total amount back to the header (#914)
* NT-1326: Reward Title going two lines (#918)
* NT-1345: Bonus support validation fixes (#917)
* NT-1345: Bonus support validation fixes (#917)
* NT-1383: New add-ons screen (#923)
* NT-1384: Add-ons list (#925)
* NT-1384- AddOns query (#927)
* NT-1411: Creator crash fixed (#929)
* NT-1385: Add Ons Card UI  (#930)
* NT-1386: Stepper UI on Add-On card (#937)
* NT-1422 && NT-1402 && NT-1383 && NT-1385 && NT-1382: Fix rejected (#946)
* NT-1386:Rejected fix (#947)
* NT-1381: Pledge header design polish (#948)
* NT-1426: Android Manage Pledge View Design Polish (#949)
* NT-1380 Bonus support design polish (#950)
* NT-1344: Updated checkout with new mutation  (#951)
* NT-1344: Updated checkout with new mutation 
* NT- 1462&& NT-1463: UpdateBacking Mutation  (#952)
* NT-1462:Update pledge flow (#954)
* NT-1445: Selected Reward Tag  (#955)
* NT-1390: Previously selected reward logic (#956)
* NT-1440:Display Empty State when add-ons unavailable (#961)
* NT-1453:Maximum pledge string updates (#962)
* NT-1460:Update add ons selection (#959)
* NT-1417: Show a native alert during Edit Reward if changes would remove add ons (#965)
* NT-1387: Fix Add-Ons Available tag for Digital Reward (#970)
* NT-1387: Fix - Select AddOns for digital reward (#971)
* [NT-1453][NT-1344][NT-1399][NT-1509]: Fix Pledge with Digital addOns  (#974)
* [NT-1417][NT-1510]:Fix change reward flow (#975)
* NT-1442: Android Display an error state if add-ons fail to load (#980)
* NT-1516: Update the Bonus Support Base Amount (#981)
* NT-1534: Sold-out add-ons (#983)
* [NT-1453] Bonus Support Max Pledge String Fix (#987)
* NT-1442: Hide shipping selector on network error (#986)
* NT-1471 | NT-1539 - Prevent Add-ons Alert & Add Pledge Label (#991)
* NT-1549 : Choose another reward flow (#993)
* NT-1539: Unprompted Edit Rewards Alert (#994)
* NT-1541: Updated Add-ons Quantity Not Updated (#995)
* NT-1534: Android Sold-out add-ons fix (#996)
* NT-1534: Modify previously backed AddOns if unavailable (#1005)
* NT-606: FIX Display a string indicating backing state for creators on View/Manage Pledge screen 
* NT-1585:Reward with starting time restriction not started yet. (#1009)
* https://kickstarter.atlassian.net/browse/NT-1587 (#1011)
* NT- 1591:Blanck screen edit reward flow (#1012)
* NT-1531: Android Refactor RewardUtils Java to Kotlin (#1008)
* NT-1587: Improve performance (#1013)
* NT-1587: Query with filtering for shippingRules (#1015)

Co-authored-by: Jade Byfield <jjbyfield@gmail.com>
Co-authored-by: Jade Byfield <jade@thoughtbot.com>
Co-authored-by: leighdouglas <leighcdouglas1@gmail.com>
Co-authored-by: jgsamudio <jonathan2457@gmail.com>
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.

2 participants
0