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

feat: Subscription settings UI #42990

Merged
merged 20 commits into from
Jun 7, 2024

Conversation

MrMuzyk
Copy link
Contributor

@MrMuzyk MrMuzyk commented Jun 3, 2024

Details

  • Implemented Subscription settings UI section on subscription screen
  • Implemented FeedbackSurvey component
  • Implemented screen displayed when user tries to disable auto-renew

Fixed Issues

$ #38626
PROPOSAL:

Tests

  • go to /settings/subscription
  • try to disable auto renew
  • Verify that no errors appear in the JS console

Offline tests

QA Steps

  • go to /settings/subscription
  • try to disable auto renew
  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
    • MacOS: Desktop
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
      • If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari Screenshot 2024-06-03 at 14 24 05 Screenshot 2024-06-03 at 14 24 17
MacOS: Desktop

Copy link
Contributor

@rezkiy37 rezkiy37 left a comment

Choose a reason for hiding this comment

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

Left comments.

@MrMuzyk MrMuzyk requested review from rezkiy37 and koko57 June 4, 2024 08:02
@MrMuzyk MrMuzyk marked this pull request as ready for review June 4, 2024 08:13
@MrMuzyk MrMuzyk requested a review from a team as a code owner June 4, 2024 08:13
@melvin-bot melvin-bot bot requested review from mollfpr and removed request for a team June 4, 2024 08:13
Copy link

melvin-bot bot commented Jun 4, 2024

@mollfpr Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@MrMuzyk MrMuzyk requested a review from fabioh8010 June 4, 2024 11:03
@mollfpr
Copy link
Contributor

mollfpr commented Jun 4, 2024

Mostly looks good. Just found a couple of issues.

  • The back button is shown on the subscription page when the disable auto-renew survey opens
Screen.Recording.2024-06-04.at.20.48.29.mp4
  • The text option in Spanish is overflow
    Screenshot 2024-06-04 at 20 53 26

  • The subscription settings page doesn't scrollable, we can add <ScrollView contentContainerStyle={styles.pt3}>. The style padding is to match the padding on the other page, between the header component and the section below.
    Screenshot 2024-06-04 at 20 53 48

  • The disable auto-renew survey is not scrollable either, and the submit button does not float when the screen is too small.

Screenshot 2024-06-04 at 21 16 03

@mollfpr
Copy link
Contributor

mollfpr commented Jun 4, 2024

The save up to text is conflicted with the selection option.

Screenshot 2024-06-04 at 21 50 02

Copy link
Contributor

@mollfpr mollfpr left a comment

Choose a reason for hiding this comment

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

LGTM 👍

@melvin-bot melvin-bot bot requested a review from amyevans June 6, 2024 12:00
Copy link
Contributor

@amyevans amyevans left a comment

Choose a reason for hiding this comment

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

Just a few minor comments!

@Expensify/design would you like to review as well?

subscriptionSettings: {
title: 'Subscription settings',
autoRenew: 'Auto-renew',
yourAnnual: 'Your annual subscription will automatically renew on (date). You can switch to pay-per-use starting 30 days before renewal.',
Copy link
Contributor

Choose a reason for hiding this comment

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

(date) should be a variable here, equal to nvp_private_subscription.endDate + 1 month

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Actually this translation key is not used anywhere 😅 It was present in the doc so I've added it but its not used anywhere so Im removing it

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 will however adjust the renewal date we display under auto-renew toggle

Copy link
Contributor

Choose a reason for hiding this comment

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

Ah okay good catch, I think that initial text was from a previous iteration (I see it in the high level portion of the doc, but not Figma or the mocks in Detailed, so I think we're good to remove it).

autoRenew: 'Auto-renew',
yourAnnual: 'Your annual subscription will automatically renew on (date). You can switch to pay-per-use starting 30 days before renewal.',
autoIncrease: 'Auto-increase annual seats',
saveUpTo: 'Save up to $10/month per active member',
Copy link
Contributor

Choose a reason for hiding this comment

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

This needs to be slightly variable: it should be 10 for a Collect plan and 18 for a Control plan. I'm also asking in the doc if it should always be in USD or not

Copy link
Contributor

Choose a reason for hiding this comment

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

Just gonna tag you here directly too @MitchExpensify 😄

Copy link
Contributor

Choose a reason for hiding this comment

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

I think this should be localised to the billing currency, personally. It doesn't make sense if you're billed in GBP.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

At the moment all prices on main Subscription page have fixed $ currency. Do you want me to fix them all as part of this PR or do we leave the currency as it is for now and change it later in a separate issue?

Copy link
Contributor

Choose a reason for hiding this comment

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

I think it's fine to be a follow-up, but let's make sure we do it.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ok, so should we create new issue for it? If so, who's job is it? :)

Copy link
Contributor

Choose a reason for hiding this comment

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

Polish GH for later follow-up: #43277

return (
<ScreenWrapper
testID={DisableAutoRenewSurveyPage.displayName}
includeSafeAreaPaddingBottom={false}
Copy link
Contributor

Choose a reason for hiding this comment

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

Could this in theory still be accessed on native via deep link? Should we implement return null for native?

@shawnborton
Copy link
Contributor

Looks like the cards are not using the max-width style that we use everywhere else:
image

@MrMuzyk
Copy link
Contributor Author

MrMuzyk commented Jun 7, 2024

Looks like the cards are not using the max-width style that we use everywhere else:

It will be fixed with next rebase. Fix for it made it to main late afternoon :)

@MrMuzyk
Copy link
Contributor Author

MrMuzyk commented Jun 7, 2024

@amyevans I've replied to/fixed whats been pointed out. Have a look when you can :)

Copy link
Contributor

@amyevans amyevans left a comment

Choose a reason for hiding this comment

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

1 small thing to go (my bad!), then we can merge!

// TODO these default state values will come from API in next phase
const [autoRenew, setAutoRenew] = useState(true);
const [autoIncrease, setAutoIncrease] = useState(false);

// TODO this will come from API in next phase
const expirationDate = format(new Date(), CONST.DATE.MONTH_DAY_YEAR_ABBR_FORMAT);
const autoRenewalDate = privateSubscription?.endDate ? format(addMonths(new Date(privateSubscription?.endDate), 1), CONST.DATE.MONTH_DAY_YEAR_ABBR_FORMAT) : '';
Copy link
Contributor

Choose a reason for hiding this comment

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

Sorry, I gave you bad info regarding adding a month to the end date. The autoRenewalDate should just be equal to the endDate (keep the formatting you've applied here though)

Copy link
Contributor

Choose a reason for hiding this comment

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

I think we need to tweak what is passed to the Date constructor? Ultimately it should say it renews on June 1, 2025 in this case
Screenshot 2024-06-07 at 9 56 42 AM

Copy link
Contributor Author

Choose a reason for hiding this comment

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

hmm, checking

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thats weird, because it is working fine on my end

image

Copy link
Contributor

@amyevans amyevans Jun 7, 2024

Choose a reason for hiding this comment

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

I think

const autoRenewalDate = privateSubscription?.endDate ? format(new Date(`${privateSubscription?.endDate}T00:00:00`), CONST.DATE.MONTH_DAY_YEAR_ABBR_FORMAT) : '';

would work, currently it's picking up my local timezone I think

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ok, I've changed it. I will be finishing for today but on monday I might get back to this (in this or one of next PRs) and refactor it to something more elegant. I believe getNewSubscriptionRenewalDate might have the same TZ issue so I will look into it

Copy link
Contributor

Choose a reason for hiding this comment

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

Okay, I'm going to merge this PR to keep things moving but definitely feel free to refactor in a follow up PR. Thank you!

@MrMuzyk MrMuzyk requested a review from amyevans June 7, 2024 14:08
@amyevans amyevans merged commit eff0783 into Expensify:main Jun 7, 2024
17 checks passed
@OSBotify
Copy link
Contributor

OSBotify commented Jun 7, 2024

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@zanyrenney
Copy link
Contributor

The submit button is unresponsive here. @MrMuzyk @mollfpr are you able to resolve this in the related GH issue- #43466

@MrMuzyk
Copy link
Contributor Author

MrMuzyk commented Jun 11, 2024

@zanyrenney

Only UI was implemented in this PR. Submit action will come in the next phase - there is a comment that serves as a reminder as well.

const handleSubmit = () => {
// TODO API call to submit feedback will be implemented in next phase
};

It might be the case that it's being already implemented in one of the PRs.

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/luacmartins in version: 1.4.81-11 🚀

platform result
🤖 android 🤖 failure ❌
🖥 desktop 🖥 success ✅
🍎 iOS 🍎 success ✅
🕸 web 🕸 success ✅

<FormAlertWithSubmitButton
isAlertVisible={shouldShowReasonError}
onSubmit={handleSubmit}
message="common.error.pleaseCompleteForm"
Copy link
Contributor

Choose a reason for hiding this comment

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

Error message here was left hardcoded, it needed translate function. #44075

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

Successfully merging this pull request may close these issues.