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

Complete Task Front End #18806

Merged
merged 39 commits into from
May 15, 2023
Merged

Complete Task Front End #18806

merged 39 commits into from
May 15, 2023

Conversation

thienlnam
Copy link
Contributor

@thienlnam thienlnam commented May 11, 2023

Details

Fixed Issues

$ #16858
PROPOSAL: GH_LINK_ISSUE(COMMENT)

Tests

  • Verify that no errors appear in the JS console
  1. Create a task

  2. Select 'Mark as done'

  3. Notice you see the task change to 'Completed'

  4. Go back to the parent chat where the task was created

  5. Notice there is a completed checkbox

  6. Create a task

  7. Go back to the parent chat where the task was created

  8. Hit the checkbox to 'complete' the task

  9. Notice that it says marked

  10. Open the task

  11. Verify you see the task is marked as 'Completed'

Offline tests

Same as online

QA Steps

Same as tests

  • 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
Screen.Recording.2023-05-15.at.9.09.50.AM.mov
Mobile Web - Chrome
Screen.Recording.2023-05-15.at.9.10.31.AM.mov
Mobile Web - Safari
Desktop
Screen.Recording.2023-05-15.at.9.12.39.AM.mov
iOS
Android

@thienlnam thienlnam self-assigned this May 11, 2023
@thienlnam thienlnam changed the title Create Task Front End Complete Task Front End May 11, 2023
@thienlnam thienlnam mentioned this pull request May 13, 2023
63 tasks
@fedirjh
Copy link
Contributor

fedirjh commented May 14, 2023

Could you please merge main. latest changes for update task are not present yet . I noticed this , there is two button , mark as complete and mark as done , is there any difference ?

Screen.Recording.2023-05-14.at.11.27.26.PM.mov

@arosiclair arosiclair merged commit 92f87f7 into main May 15, 2023
@arosiclair arosiclair deleted the jack-completeTask branch May 15, 2023 21:01
task: {
completed: 'Completada',
messages: {
completed: 'tarea completada',
Copy link
Contributor

Choose a reason for hiding this comment

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

Should Tarea be capitalized? in the english translations we have Completed as capitalized

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good catch, @arosiclair since this is small, could you also add this onto your PR for cancel task?

@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/arosiclair in version: 1.3.15-0 🚀

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

@isagoico
Copy link

@thienlnam Hi! We found these 2 issues when executing this PR

#19150
#19149

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/yuwenmemon in version: 1.3.15-12 🚀

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

@mananjadhav
Copy link
Collaborator

mananjadhav commented Jun 1, 2023

When we added MenuItemWithTopDescription we didn't use translation for Task and Description. Hence this resulted in #18690.

I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

We have the checklist item, but I think we still missed adding for these two labels.

@mollfpr
Copy link
Contributor

mollfpr commented Jun 29, 2023

✋ Coming from #19631

The assignee name/email is empty for the non-assignee or non-owner user on the task header.

@sobitneupane
Copy link
Contributor

This small issue was not handled in this PR while adding Task Header.

Issue: Only description's text has reduced opacity when it's disabled

@sobitneupane
Copy link
Contributor

This issue was not handled in this PR while adding lastMessageText.

Issue: Reopened task message does not translate to Spanish in LHN

Comment on lines +59 to +64
<Avatar
source={assigneeAvatar}
type={CONST.ICON_TYPE_AVATAR}
name={assigneeName}
size={CONST.AVATAR_SIZE.HEADER}
/>
Copy link
Contributor

Choose a reason for hiding this comment

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

This caused a regression. Previously we used TaskSelectorLink -> MultipleAvatars. And MultipleAvatars wraps the Avatar with a Tooltip

<Tooltip text={props.avatarTooltips[0]}>
Now we are missing the tooltip (Coming from #21713).

Comment on lines +169 to +175
onyxMethod: Onyx.METHOD.MERGE,
key: `${ONYXKEYS.COLLECTION.REPORT}${parentReportID}`,
value: {
lastVisibleActionCreated: completedTaskReportAction.created,
lastMessageText: message,
lastActorEmail: completedTaskReportAction.actorEmail,
},
Copy link
Contributor

Choose a reason for hiding this comment

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

This is missing the childVisibleActionCount to update the number of replies in the thread.

@@ -68,7 +70,10 @@ const TaskPreview = (props) => {
containerStyle={[styles.taskCheckbox]}
isChecked={isTaskCompleted}
onPress={() => {
Copy link
Member

Choose a reason for hiding this comment

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

Coming from Unauthorized Task Reopening by Anonymous User in Incognito Mode- Inconsistency

We should have checked if an anonymous user is trying to mark a task as completed.

Copy link
Contributor

Choose a reason for hiding this comment

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

The implementation of the anonymous user was done after this PR :

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.