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

#26793: show selected tag even if all are disabled #28151

Merged

Conversation

BeeMargarida
Copy link
Contributor

Details

There was a wrong behaviour happening, this PR fixes it. Mentioned in https://callstack-hq.slack.com/archives/C02MW39LT9N/p1695649373962089?thread_ts=1695632734.639029&cid=C02MW39LT9N.

Expected behaviour:
When editing a money request with a previously selected tag, if all tags are disabled, it should show the previously selected tag in the picker and allow to de-select it.

Current behaviour (before this PR):
When editing a money request with a previously selected tag, if all tags are disabled, it showed an empty list, with no currently selected option.

Fixed Issues

$ #26793

Tests

Requires 3 things:

  • Have access to the newDotTags beta
  • Have a workspace with tags setup
  • Do the following setup in the collapsable below

Note: the edit tag behaviour is not yet supported in the backend, so the edit tag action won't be saved between reloads.

Mock disabled tags when editing a money request
  1. Go to a workspace page
  2. Copy the workspace/policyID in the URL
  3. In EditRequestPage.js add the following code
    useEffect(() => {
        Onyx.set('policyTags_<POLICY_ID>', {
            Department: {
                name: 'Department',
                tags: {
                    Accounting: {
                        name: 'Accounting',
                        enabled: false,
                    },
                    Design: {
                        name: 'Design',
                        enabled: false,
                    },
                    Engineering: {
                        name: 'Engineering',
                        enabled: false,
                    },
                    HR: {
                        name: 'HR',
                        enabled: false,
                    },
                    Infra: {
                        name: 'Infra',
                        enabled: false,
                    },
                    Legal: {
                        name: 'Legal',
                        enabled: false,
                    },
                    Marketing: {
                        name: 'Marketing',
                        enabled: false,
                    },
                    Ops: {
                        name: 'Ops',
                        enabled: false,
                    },
                    Sales: {
                        name: 'Sales',
                        enabled: false,
                    },
                },
            },
        });
    }, []);

  1. Make a money request with a tag or use a previously created one that contains a tag
  2. Enter the money request report, to edit it
  3. Click on the tag menu item
  4. It should show the picker with only the currently selected tag (should appear selected)
  5. Click on the selected tag
  6. It should navigate back, de-select the tag and hide the tag menu item (since no tags are available)
  • Verify that no errors appear in the JS console

Offline tests

Same as above

QA Steps

  1. Make a money request with a tag or use a previously created one that contains a tag
  2. Enter the money request report, to edit it
  3. Click on the tag menu item
  4. It should show the picker with only the currently selected tag (should appear selected)
  5. Click on the selected tag
  6. It should navigate back, de-select the tag and hide the tag menu item (since no tags are available)
  • 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
    • If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
    • 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 author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web
w_t.mp4
Mobile Web - Chrome
mc_t.mp4
Mobile Web - Safari
ms_t.mp4
Desktop
desk_t.mp4
iOS
ios_t.mp4
Android
android_t.mp4

@amyevans amyevans self-requested a review September 26, 2023 02:00
@BeeMargarida BeeMargarida marked this pull request as ready for review September 26, 2023 08:57
@BeeMargarida BeeMargarida requested a review from a team as a code owner September 26, 2023 08:57
@melvin-bot melvin-bot bot requested review from parasharrajat and removed request for a team September 26, 2023 08:57
@melvin-bot
Copy link

melvin-bot bot commented Sep 26, 2023

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

@parasharrajat
Copy link
Member

Reviewing it....

@amyevans
Copy link
Contributor

Thanks for the fix @BeeMargarida! @parasharrajat please still review and complete the checklist

@parasharrajat
Copy link
Member

parasharrajat commented Sep 26, 2023

Have access to the newDotTags beta
Have a workspace with tags setup
Do the following setup in the collapsable below

How can I get that? I force-enabled the beta from the permissions file but don't know how to do 2nd step.

@amyevans
Copy link
Contributor

@parasharrajat Sorry, it's an either/or actually,

Either:

  1. Have access to the newDotTags beta and 2. Have a workspace with tags setup

OR you can mock it with:

  1. Do the following setup in the collapsable below

To set up a workspace with tags, you can:

  1. Go to OldDot (expensify.com) and open or create a Control policy
  2. In the JS console with the policy open do:
  3. p = Policy.getCurrent();
  4. p.policy.isPolicyExpenseChatEnabled = "true";
  5. p.save();
  6. Go to Policies > Tags and add tags to your policy
  7. Go to Policies > People and invite a new user to the policy
  8. Sign into that new user account in NewDot
  9. Go through the request money flow and choose the policy that you just created
  10. You now have a manual request on your Control workspace!

@parasharrajat
Copy link
Member

Let me try. Thanks for the details.

@parasharrajat
Copy link
Member

parasharrajat commented Sep 27, 2023

Resolved

So I noticed when we click the tag from the list, the tag section is removed from the request details view and it seems the tag is also removed as per the message.
Screenshot 2023-09-28 at 2 21 36 AM

but if I enable the tag back, the tag sections come back to view with the same tag value that we deselected. it does not look correct as we already removed it and a message has been shown to the user already. Now, there should be no tag.

@BeeMargarida

@parasharrajat
Copy link
Member

parasharrajat commented Sep 27, 2023

My bad, I just noticed there is no API logic to reset the value so it is just a UI change. We are good here.

@parasharrajat
Copy link
Member

parasharrajat commented Sep 27, 2023

Screenshots

🔲 iOS / native

Screen.Recording.2023-09-28.at.2.48.56.AM.mov

🔲 iOS / Safari

Screen.Recording.2023-09-28.at.2.30.21.AM.mov

🔲 MacOS / Desktop

Screen.Recording.2023-09-28.at.2.40.14.AM.mov

🔲 MacOS / Chrome

Screen.Recording.2023-09-28.at.2.29.11.AM.mov

🔲 Android / Chrome

Screen.Recording.2023-09-28.at.2.30.49.AM.mov

🔲 Android / native

Screen.Recording.2023-09-28.at.2.53.38.AM.mov

Copy link
Member

@parasharrajat parasharrajat left a comment

Choose a reason for hiding this comment

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

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.

🎀 👀 🎀 C+ reviewed

@amyevans amyevans merged commit 87e6a80 into Expensify:main Sep 28, 2023
13 of 14 checks passed
@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

🚀 Deployed to staging by https://github.com/amyevans in version: 1.3.75-0 🚀

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

@OSBotify
Copy link
Contributor

OSBotify commented Oct 2, 2023

🚀 Deployed to production by https://github.com/mountiny in version: 1.3.75-12 🚀

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

@OSBotify
Copy link
Contributor

OSBotify commented Oct 2, 2023

🚀 Deployed to staging by https://github.com/amyevans in version: 1.3.76-0 🚀

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

@OSBotify
Copy link
Contributor

OSBotify commented Oct 3, 2023

🚀 Deployed to production by https://github.com/mountiny in version: 1.3.76-6 🚀

platform result
🤖 android 🤖 success ✅
🖥 desktop 🖥 success ✅
🍎 iOS 🍎 failure ❌
🕸 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