Skip to content

Conversation

@robertKozik
Copy link
Contributor

@robertKozik robertKozik commented May 11, 2023

Details

This PR migrates the soon-to-be deprecated TouchableOpacity to the PressableWithFeedback component. Changes the AccessibilityLabel of BaseGenericPressable to be required only when component is set to be accessible.

Fixed Issues

$ #17018
PROPOSAL: #17018

Tests

Make sure that every instance of CheckboxWithLabel is working correctly (fe. enablePaymentPage when adding debit card as new payment method)

  1. Access the screen with instance of CheckboxWithLabel
  2. Click on the text next to the checkbox
  3. Verify that state of checkbox has changed
  • Verify that no errors appear in the JS console

Offline tests

SAME AS TEST STEPS

QA Steps

SAME AS TEST STEPS

  • 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 / Chrome
    • iOS / native
    • iOS / 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 approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
    • 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 a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately and each prop has a /** comment above it */
    • The file is named correctly
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
    • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
    • All JSX used for rendering exists in the render method
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • 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(themeColors.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 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.
  • I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web
Desktop.-.web.mov
Mobile Web - Chrome
Android.-.chrome.mov
Mobile Web - Safari
iOS.-.safari.mov
Desktop
Desktop.-.electron.mov
iOS
iOS.-.native.mov
Android
Android.-.native.mov

@melvin-bot
Copy link

melvin-bot bot commented May 11, 2023

Hey! I see that you made changes to our Form component. Make sure to update the docs in FORMS.md accordingly. Cheers!

@robertKozik robertKozik marked this pull request as ready for review May 15, 2023 08:24
@robertKozik robertKozik requested a review from a team as a code owner May 15, 2023 08:24
@melvin-bot melvin-bot bot requested review from Santhosh-Sellavel and marcaaron and removed request for a team May 15, 2023 08:24
@melvin-bot
Copy link

melvin-bot bot commented May 15, 2023

@Santhosh-Sellavel @marcaaron One of you needs to 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]

@Santhosh-Sellavel
Copy link
Collaborator

@robertKozik

Checkbox label gets cropped off

Screenshot 2023-05-16 at 12 10 56 AM

Before

Screenshot 2023-05-16 at 12 10 41 AM

Copy link
Collaborator

@Santhosh-Sellavel Santhosh-Sellavel left a comment

Choose a reason for hiding this comment

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

Please address this

@robertKozik
Copy link
Contributor Author

I wasn't sure on which device you were testing but after changes I've checked it on web inside resonsive design tool:

test on responsivnes
Screen.Recording.2023-05-15.at.23.30.52.mov

@Santhosh-Sellavel
Copy link
Collaborator

Santhosh-Sellavel commented May 17, 2023

Thanks, @robertKozik this was from the web/desktop.

On iOS/Android it is still broken.

Before

Simulator Screenshot - iPhone 14 - 2023-05-17 at 06 21 29

Now

Simulator Screenshot - iPhone 14 - 2023-05-17 at 06 21 08

Content is overflowing outside the padding on the right side.

@robertKozik
Copy link
Contributor Author

I saw lint is not failing, I'll handle it asap

@Santhosh-Sellavel
Copy link
Collaborator

Santhosh-Sellavel commented May 17, 2023

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible 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 checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified tests pass on all platforms & I tested again on:
    • Android / native
    • Android / Chrome
    • iOS / native
    • iOS / Safari
    • MacOS / Chrome / Safari
    • MacOS / Desktop
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified proper code patterns were followed (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
    • 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 approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
    • 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 verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • 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
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately and each prop has a /** comment above it */
    • The file is named correctly
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
    • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
    • All JSX used for rendering exists in the render method
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • 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(themeColors.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 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.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Web & Desktop
Screen.Recording.2023-05-17.at.11.45.55.PM.mov
Mobile Web - Chrome
Screen_Recording_20230518_000723_Chrome.mp4
Mobile Web - Safari & iOS
Simulator.Screen.Recording.-.iPhone.14.-.2023-05-18.at.00.08.54.mp4
Android
Screen_Recording_20230518_001843_New.Expensify.mp4

Copy link
Collaborator

@Santhosh-Sellavel Santhosh-Sellavel 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, and tests well.

It is not working on the storybook. Seems it's not been updated for a while. What should we do here @marcaaron

@robertKozik
Copy link
Contributor Author

I checked the storybook problem, and it's easily solvable, so I'll include it in a sec

@Santhosh-Sellavel
Copy link
Collaborator

@robertKozik

Still IsChecked controls don't work as it works for Checkbox.

Screen.Recording.2023-05-19.at.1.43.07.AM.mov

cc: @marcaaron

@robertKozik
Copy link
Contributor Author

CheckboxWithLabel due to some previous updates self manages its state. Passed isChecked prop is just kind of "default state" as I saw how its working

@Santhosh-Sellavel
Copy link
Collaborator

@marcaaron What should we do here?

@marcaaron marcaaron removed their request for review May 22, 2023 21:29
Copy link
Contributor

@roryabraham roryabraham left a comment

Choose a reason for hiding this comment

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

Can we please:

  • Migrate CheckboxWithLabel to a function component.
  • Update isChecked state when the passed-in isChecked prop changes:
useEffect(() => setIsChecked(props.isChecked), [props.isChecked]);

@robertKozik
Copy link
Contributor Author

Sure no problem, I'll do it today.

@robertKozik
Copy link
Contributor Author

All requested changes are implemented, but when starting storybook I've encountered an error

ERR! Error: ENOENT: no such file or directory, open '/Users/robertkozik/sw-projects/Expensify_app_fork/assets/images/new-expensifyundefined.svg'

as I check its related with choosing the splashLogo inside webpack.common.js in mapEnvToLogoSuffix function. Does it occur for you too, or it's problem on my side? if not I can create the bug report for it

Regardless, after coping with that problem CheckboxWithLabel is working fine in the storybook.

@Santhosh-Sellavel
Copy link
Collaborator

@robertKozik Conflicts here, please resolve when you get a chance! I'll get through the checklist tomorrow!

@Santhosh-Sellavel
Copy link
Collaborator

All requested changes are implemented, but when starting storybook I've encountered an error

ERR! Error: ENOENT: no such file or directory, open '/Users/robertkozik/sw-projects/Expensify_app_fork/assets/images/new-expensifyundefined.svg'

as I check its related with choosing the splashLogo inside webpack.common.js in mapEnvToLogoSuffix function. Does it occur for you too, or it's problem on my side? if not I can create the bug report for it

Regardless, after coping with that problem CheckboxWithLabel is working fine in the storybook.

This occurs to me, please report it. And yes CheckboxWithLabel looks good on the storybook after fixing the error!

Copy link
Collaborator

@Santhosh-Sellavel Santhosh-Sellavel left a comment

Choose a reason for hiding this comment

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

LGTM tests well!

@Santhosh-Sellavel
Copy link
Collaborator

All your @roryabraham!

@roryabraham roryabraham merged commit 2f9cc6d into Expensify:main May 31, 2023
@OSBotify
Copy link
Contributor

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

@OSBotify
Copy link
Contributor

OSBotify commented Jun 1, 2023

🚀 Deployed to staging by https://github.com/roryabraham in version: 1.3.22-0 🚀

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

@OSBotify
Copy link
Contributor

OSBotify commented Jun 2, 2023

🚀 Deployed to production by https://github.com/Julesssss in version: 1.3.22-1 🚀

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

2 similar comments
@OSBotify
Copy link
Contributor

OSBotify commented Jun 2, 2023

🚀 Deployed to production by https://github.com/Julesssss in version: 1.3.22-1 🚀

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

@OSBotify
Copy link
Contributor

OSBotify commented Jun 2, 2023

🚀 Deployed to production by https://github.com/Julesssss in version: 1.3.22-1 🚀

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

/>
<PressableWithFeedback
focusable={false}
accessible={false}
Copy link
Contributor

@aimane-chnaif aimane-chnaif Jun 5, 2023

Choose a reason for hiding this comment

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

Coming from #20153:

                    accessible={false}

@robertKozik Is this intentional or temporary solution to fix console error?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It's intentional, we have checkbox accessible and focusable itself. I wanted to remove two accessible views one next to another, which are doing the same

const CheckboxWithLabel = (props) => {
// We need to pick the first value that is strictly a boolean
// https://github.com/Expensify/App/issues/16885#issuecomment-1520846065
const [isChecked, setIsChecked] = useState(_.find([props.value, props.defaultValue, props.isChecked], (value) => _.isBoolean(value)));
Copy link
Contributor

Choose a reason for hiding this comment

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

We also need to check the case when the checkbox is controlled or uncontrolled.

More details here:

#73894 (comment)

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.

6 participants