[HOLD for payment 2023-08-28] [$250] Migrate index.js to function component

[marcaaron]

Class Component Migration

Filenames

• src/components/Composer/index.js
  • type: React.Component
  • has state values: true
  • has refs: true
  • has context: false
  • lifecycle methods: componentDidMount,componentWillUnmount,componentDidUpdate

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

[s-alves10]

I'd love to work on this.

[GiovanniCaiazzo01]

hey I'd like to work on this task

[melvin-bot]

📣 @GiovanniCaiazzo01! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:

1. Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
2. Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
3. Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
   
   Format:

Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>

[GiovanniCaiazzo01]

Contributor details
Your Expensify account email: giovannicaiazzo002@gmail.com
Upwork Profile Link: https://www.upwork.com/freelancers/~01572883c97205ee25

[melvin-bot]

✅ Contributor details stored successfully. Thank you for contributing to Expensify!

[perunt]

hey there, I'm currently developing the inline suggestion feature and this task is creating a bit of a hold-up for me. Could I jump in and expedite its completion?

[rayane-djouah]

I'd like to work on this issue

[mkhutornyi]

I'd like to work on this.

[dayana7204]

I am ready to work on this ticket :)

[code0406]

I am available to work on this.

[aditygrg2]

Hello, I would like to work on this issue.

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

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

• Migrate Composer. web #23359

If no regressions arise, payment will be issued on 2023-08-28. 🎊

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

For reference, here are some details about the assignees on this issue:

• @ArekChr does not require payment (Contractor)
• @allroundexperts does not require payment (Eligible for Manual Requests)
• @perunt does not require payment (Contractor)

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

[melvin-bot]

@ArekChr, @allroundexperts, @perunt Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[melvin-bot]

@ArekChr, @allroundexperts, @perunt Still overdue 6 days?! Let's take care of this!

[melvin-bot]

@ArekChr, @allroundexperts, @perunt 12 days overdue now... This issue's end is nigh!

[melvin-bot]

@ArekChr, @allroundexperts, @perunt 12 days overdue now... This issue's end is nigh!

[perunt]

It's already been merged and used in production. Can we close this ticket?

[melvin-bot]

@ArekChr, @allroundexperts, @perunt Whoops! This issue is 2 days overdue. Let's get this updated quick!

[melvin-bot]

@ArekChr, @allroundexperts, @perunt Still overdue 6 days?! Let's take care of this!

[melvin-bot]

@ArekChr, @allroundexperts, @perunt Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it!

[perunt]

@mountiny, can we mark this issue as resolved? We've been using it in production for some time now, so I believe we can close it