[HOLD for payment 2023-12-12] [TS migration] Migrate 'LocalNotification' lib to TypeScript

[melvin-bot]

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

Path	Dependencies
src/libs/Notification/LocalNotification/index.website.js	1
src/libs/Notification/LocalNotification/index.native.js	0
src/libs/Notification/LocalNotification/index.desktop.js	1
src/libs/Notification/LocalNotification/BrowserNotifications.js	6
src/libs/Notification/LocalNotification/focusApp/index.website.js	0
src/libs/Notification/LocalNotification/focusApp/index.desktop.js	1

Issue Owner

Current Issue Owner: @MitchExpensify

[melvin-bot]

This issue has not been updated in over 15 days. eroding to Monthly issue.

P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

[kubabutkiewicz]

Hi, I'm Jakub from Callstack - expert contributor group - and I would like to take a look at this issue.

[melvin-bot]

@melvin-bot[bot], this Monthly task hasn't been acted upon in 6 weeks; closing.

If you disagree, feel encouraged to reopen it -- but pick your least important issue to close instead.

[melvin-bot]

Triggered auto assignment to @MitchExpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[melvin-bot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[mountiny]

$250 to @fedirjh once deployed with no regressions

[melvin-bot]

@kubabutkiewicz, @mountiny, @MitchExpensify, @fedirjh Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[mountiny]

issue was linked incorrectly, this is ready for payment @MitchExpensify

[MitchExpensify]

Payment issue created for you here and invited @fedirjh https://www.upwork.com/jobs/~01c91332994586a049

[Garretrein]

Hi, My name is David, As a Full stack software engineer, i am interested of this issue.
I quite sure that i can resolve this issue.

[melvin-bot]

📣 @Garretrein! 📣
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>

[fedirjh]

@MitchExpensify Thank you. Accepted.

[Davnbrown]

Hello, My name is David Brown.
https://www.upwork.com/freelancers/~01459846037723f7ae

[melvin-bot]

📣 @Davnbrown! 📣
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>

[MitchExpensify]

Paid and contract ended!

[Davnbrown]

Contributor details
Your Expensify account email: [email protected]
Upwork Profile Link: https://www.upwork.com/freelancers/~01459846037723f7ae

[melvin-bot]

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

[Davnbrown]

now how can I do?

[fedirjh]

@Davnbrown This issue was already addressed. Please check other open issues (open jobs), please make sure to read the contributing Guides. Thank you!

[MitchExpensify]

Apologies for any confusion, no help needed here @Davnbrown