[HOLD for payment 2024-03-22] [$250] [TS migration] Migrate VideoPlayerContexts component files to TypeScript

[hayata-suenaga]

TypeScript migration

Make sure you read through our TypeScript's style guide, cheatsheet and PropTypes conversion table before you start working on this migration issue.

Files related to the VideoPlayerContexts component

• src/components/VideoPlayerContexts/PlaybackContext.js
• src/components/VideoPlayerContexts/VideoPopoverMenuContext.js
• src/components/VideoPlayerContexts/VolumeContext.js

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01981a2129abb4828c
• Upwork Job ID: 1758559484183658496
• Last Price Increase: 2024-02-16

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~01981a2129abb4828c

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @eVoloshchak (External)

[ghost]

Dibs

[MahmudjonToraqulov]

Would like to work on it.

[rayane-d]

dips

[ZhenjaHorbach]

I can work on it
And I don't have others TS issues assigned to me

[EnderKilledYou]

Proposal

Update the Video player component to type script following the style guide.

Please re-state the problem that we are trying to solve in this issue.

We want uniform language throughout the app.

What is the root cause of that problem?

Files are not in type script

What changes do you think we should make in order to solve the problem?

Change them to typescript

What alternative solutions did you explore? (Optional)

Maybe changing them to blazor.

[Koustubh-lapate]

I am Koustubh, a full stack developer. I’d like to work on this job.

[kowczarz]

Hello! I'm Kamil Owczarz from Software Mansion, the expert agency and I would like to work on this issue.

[suneox]

I don't have any other TS migration assigned so would like to work on this ticket

[kowczarz]

Hey @hayata-suenaga, I'm leaving the Expensify-SWM team for now and @smelaa will handle this task.

[smelaa]

Hello! I'm Aleksandra Smela from Software Mansion, the expert agency and I would like to work on this issue.

[melvin-bot]

📣 @smelaa! 📣
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. Make sure you've read and understood the contributing guidelines.
2. 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.
3. 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.
4. 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>

[melvin-bot]

The BZ member will need to manually hire smelaa for the Contributor role. Please store your Upwork details and apply to our Upwork job so this process is automatic in the future!

[melvin-bot]

@eVoloshchak, @hayata-suenaga, @smelaa Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[hayata-suenaga]

The BZ member will need to manually hire smelaa for the Contributor role. Please store your Upwork details and apply to our Upwork job so this process is automatic in the future!

No need to hire smelaa. They're from Software Mansion, one of the expert agencies.

[melvin-bot]

@eVoloshchak, @hayata-suenaga, @smelaa Whoops! This issue is 2 days overdue. Let's get this updated quick!

[hayata-suenaga]

@smelaa please mark the PR ready for review once it's ready 🙇

[melvin-bot]

Triggered auto assignment to @bfitzexpensify (NewFeature), see https://stackoverflowteams.com/c/expensify/questions/14418#:~:text=BugZero%20process%20steps%20for%20feature%20requests for more details.

[hayata-suenaga]

@bfitzexpensify

needs payment for @eVoloshchak who is a C+ who reviewed the TypeScript migration PR. The PR author is an expert agency engineer and no need for payment

[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.4.52-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [TS migration] Migrate VideoPlayerContexts component files to TypeScript #37134

If no regressions arise, payment will be issued on 2024-03-22. 🎊

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

• @eVoloshchak requires payment through NewDot Manual Requests
• @smelaa does not require payment (Contractor)

[melvin-bot]

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

• [@eVoloshchak] Please propose regression test steps to ensure the new feature will work correctly on production in further releases.
• [@bfitzexpensify] Link the GH issue for creating/updating the regression test once above steps have been agreed upon.

[bfitzexpensify]

Payment summary:

@eVoloshchak to be paid $250 via manual request
@smelaa does not require payment (contractor)

[JmillsExpensify]

$250 approved for @eVoloshchak.