Skip to content

[HOLD for payment 2023-07-14] [$250] Migrate NewChatPage.js to function component #16239

Closed

Description

@marcaaron

Class Component Migration

Filenames

  • src/pages/NewChatPage.js
    • type: React.Component
    • has state values: true
    • has refs: false
    • has context: false
    • lifecycle methods: none

Task

  • We currently have some class components in our codebase that we would like to refactor to a function component.
  • Here's a link with some general advice on how to refactor a class component to a function component: https://react.dev/reference/react/Component#alternatives
  • If you need additional guidance, please ask in #expensify-open-source
  • Test for any regressions and verify that there are no breaking changes
Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~013e875c428c833da0
  • Upwork Job ID: 1664707231797780480
  • Last Price Increase: 2023-06-02

Activity

  1. locked and limited conversation to collaborators on Mar 20, 2023
  2. self-assigned this
    on Mar 20, 2023
  3. unlocked this conversation on Mar 21, 2023
  4. changed the title [-][HOLD] Migrate NewChatPage.js to function component[/-] [+][HOLD][$250] Migrate NewChatPage.js to function component[/+] on Apr 13, 2023
  5. marcaaron commented on Apr 13, 2023

    @marcaaron
    ContributorAuthor

    Heads up! The pricing for this issue has been adjusted based on the scope of the work and the fact that no complex bug investigations or proposal are required.

  6. thienlnam commented on Apr 13, 2023

    @thienlnam
    Contributor

    Thanks @marcaaron! I will have to counter your offer, unfortunately I can only do this for the original $1000. Thank you for your consideration and please let me know

  7. marcaaron commented on Apr 13, 2023

    @marcaaron
    ContributorAuthor

    👢

  8. changed the title [-][HOLD][$250] Migrate NewChatPage.js to function component[/-] [+][$250] Migrate NewChatPage.js to function component[/+] on Jun 2, 2023
  9. marcaaron commented on Jun 2, 2023

    @marcaaron
    ContributorAuthor

    Heads up, I'm taking this issue off HOLD and making it a Daily. If you are unable to work on it please remove your assignment and add the External + Help Wanted labels as per this update.

  10. 77 remaining items

  11. changed the title [-][$250] Migrate NewChatPage.js to function component[/-] [+][HOLD for payment 2023-07-14] [$250] Migrate NewChatPage.js to function component[/+] on Jul 7, 2023
  12. melvin-bot commented on Jul 7, 2023

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.37-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2023-07-14. 🎊

    After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.

    • External issue reporter
    • Contributor that fixed the issue
    • Contributor+ that helped on the issue and/or PR

    As a reminder, here are the bonuses/penalties that should be applied for any External issue:

    • Merged PR within 3 business days of assignment - 50% bonus
    • Merged PR more than 9 business days after assignment - 50% penalty
  13. melvin-bot commented on Jul 7, 2023

    @melvin-bot

    BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

    • [@aimane-chnaif] The PR that introduced the bug has been identified. Link to the PR:
    • [@aimane-chnaif] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
    • [@aimane-chnaif] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
    • [@aimane-chnaif] Determine if we should create a regression test for this bug.
    • [@aimane-chnaif] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
    • [@twisterdotcom / @greg-schroeder] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
  14. Nikhil-Vats commented on Jul 14, 2023

    @Nikhil-Vats
    Contributor
  15. aimane-chnaif commented on Jul 14, 2023

    @aimane-chnaif
    Contributor
  16. twisterdotcom commented on Jul 14, 2023

    @twisterdotcom
    Contributor

    Yes sorry, it's the newDot payment one. Just for my own sanity @aimane-chnaif!

  17. twisterdotcom commented on Jul 17, 2023

    @twisterdotcom
    Contributor

    Paid out!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributorImprovementItem broken or needs improvement.

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions