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

Show child tags indented on the Tag list #32337

Merged
merged 4 commits into from
Dec 4, 2023

Conversation

wlegolas
Copy link
Contributor

@wlegolas wlegolas commented Dec 1, 2023

Details

  • Change método getTagsOptions to generate the Tag options indented if the tag is in the format parent: child
  • Add Unit Tests to validate the format of generated Tag options when there are tags with the format parent: child
  • Rename the method from getCategoryOptionTree to getIndentedOptionTree in the OptionsListUtils

Fixed Issues

$ #31753
PROPOSAL: #31753 (comment)

Tests

Pre-condition: The Workspace has Tags with the format parent: child

  1. Log in to ND as an employee
  2. Navigate to Workspace chat
  3. Tap the "+" > Request money
  4. Enter the amount
  5. On the confirmation screen, tap the "Show more" button
  6. Select "Tags"
  7. Verify that tags with the format parent: child are showing indented
  • Verify that no errors appear in the JS console

Offline tests

Pre-condition: The Workspace has Tags with the format parent: child

  1. Log in to ND as an employee
  2. Navigate to Workspace chat
  3. Turn off your network connection
  4. Tap the "+" > Request money
  5. Enter the amount
  6. On the confirmation screen, tap the "Show more" button
  7. Select "Tags"
  8. Verify that tags with the format parent: child are showing indented
  • Verify that no errors appear in the JS console

QA Steps

Pre-condition: The Workspace has Tags with the format parent: child

  1. Log in to ND as an employee
  2. Navigate to Workspace chat
  3. Tap the "+" > Request money
  4. Enter the amount
  5. On the confirmation screen, tap the "Show more" button
  6. Select "Tags"
  7. Verify that tags with the format parent: child are showing indented
  • 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 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 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 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 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
test-evidence-Android-Native.mov
Android: mWeb Chrome
test-evidence-Android-mWeb-Chrome.mp4
iOS: Native
test-evidence-iOS-Native.mp4
iOS: mWeb Safari
test-evidence-iOS-mWeb-Safari.mp4
MacOS: Chrome / Safari

Chrome:

test-evidence-MacOS-Chrome.mp4

Safari

test-evidence-MacOS-Safari.mp4
MacOS: Desktop
test-evidence-MacOS-Desktop.mp4
MacOS: Chrome - Regression testing for Categories
regression-testing-for-categories.mov

@wlegolas wlegolas requested a review from a team as a code owner December 1, 2023 10:56
@melvin-bot melvin-bot bot requested review from c3024 and removed request for a team December 1, 2023 10:56
Copy link

melvin-bot bot commented Dec 1, 2023

@c3024 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]

@c3024
Copy link
Contributor

c3024 commented Dec 1, 2023

Ensure that Tags with the format parent: child are showing indented

There is no checkbox for this. The checkbox is to verify that there are no errors in console in the template. Please do not modify the template significantly. I appreciate adding unit tests and the test for checking category indentation.

Please add this as another point as "Verify that tags with the format parent: child are showing indented" after "Select Tags" like

  1. Select tags
  2. Verify that tags with the format parent: child are showing indented

Sample guidelines for test steps are here

Checkbox in QA tests section is not ticked. Also that checkbox is for no errors in console.

@c3024
Copy link
Contributor

c3024 commented Dec 1, 2023

Please fetch main because this test is failing.

@c3024
Copy link
Contributor

c3024 commented Dec 1, 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: mWeb Chrome
    • iOS: Native
    • iOS: mWeb 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 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 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

Android: Native Screenshot 2023-12-02 at 7 42 41 AM
Android: mWeb Chrome Screenshot 2023-12-01 at 9 16 40 PM
iOS: Native Screenshot 2023-12-01 at 9 10 05 PM
iOS: mWeb Safari Screenshot 2023-12-01 at 8 53 45 PM
MacOS: Chrome / Safari macChrome
MacOS: Desktop Screenshot 2023-12-01 at 8 47 22 PM

@@ -753,7 +753,7 @@ function sortTags(tags) {
* @param {Boolean} [isOneLine] - a flag to determine if text should be one line
Copy link
Contributor

@c3024 c3024 Dec 2, 2023

Choose a reason for hiding this comment

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

Please change the function description to a more generic description instead of one specifically for category to something like
"Builds the options for the tree hierarchy via indents"

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Hi, @c3024 sorry I forgot to change this description.

Done: 3f5b02487

@c3024
Copy link
Contributor

c3024 commented Dec 2, 2023

@wlegolas please check the suggestions.

@wlegolas
Copy link
Contributor Author

wlegolas commented Dec 3, 2023

Ensure that Tags with the format parent: child are showing indented

There is no checkbox for this. The checkbox is to verify that there are no errors in console in the template. Please do not modify the template significantly. I appreciate adding unit tests and the test for checking category indentation.

Please add this as another point as "Verify that tags with the format parent: child are showing indented" after "Select Tags" like

  1. Select tags
  2. Verify that tags with the format parent: child are showing indented

Sample guidelines for test steps are here

Checkbox in QA tests section is not ticked. Also that checkbox is for no errors in console.

Hi @c3024, thank you for your points, I changed the PR comment with your suggestions.

@wlegolas
Copy link
Contributor Author

wlegolas commented Dec 3, 2023

I appreciate adding unit tests and the test for checking category indentation.

Hi, @c3024 I didn't add tests for checking category indentation because the test below already validates the category indentation.

const largeResult = OptionsListUtils.getFilteredOptions(
REPORTS,
PERSONAL_DETAILS,
[],
emptySearch,
selectedOptions,
[],
false,
false,
true,
largeCategoriesList,
recentlyUsedCategories,
);
expect(largeResult.categoryOptions).toStrictEqual(largeResultList);

Have you seen another type of test that the test above doesn't cover?

@c3024
Copy link
Contributor

c3024 commented Dec 3, 2023

Thanks @wlegolas for the changes.

didn't add tests for checking category indentation because the test below already validates the category indentation.

Sorry for being unclear. I meant the regression test video for categories added in the Screenshots/Videos section. Thank you for adding a video verifying category as well after the change.

@c3024
Copy link
Contributor

c3024 commented Dec 3, 2023

LGTM

@wlegolas
Copy link
Contributor Author

wlegolas commented Dec 4, 2023

Hi @neil-marcellini if you have any questions or suggestions, please let me know.

Copy link
Contributor

@neil-marcellini neil-marcellini left a comment

Choose a reason for hiding this comment

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

Looks great thank you!

@neil-marcellini neil-marcellini merged commit a4d9bc0 into Expensify:main Dec 4, 2023
16 of 17 checks passed
@OSBotify
Copy link
Contributor

OSBotify commented Dec 4, 2023

✋ 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 Dec 5, 2023

🚀 Cherry-picked to staging by https://github.com/yuwenmemon in version: 1.4.7-4 🚀

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

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

@OSBotify
Copy link
Contributor

OSBotify commented Dec 5, 2023

🚀 Deployed to staging by https://github.com/neil-marcellini in version: 1.4.8-0 🚀

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

@wlegolas wlegolas deleted the bugfix/issue-31753 branch December 6, 2023 10:42
@OSBotify
Copy link
Contributor

OSBotify commented Dec 6, 2023

🚀 Deployed to production by https://github.com/yuwenmemon in version: 1.4.8-3 🚀

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

@OSBotify
Copy link
Contributor

OSBotify commented Dec 6, 2023

🚀 Deployed to production by https://github.com/yuwenmemon in version: 1.4.8-3 🚀

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

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.

4 participants