Closed melvin-bot[bot] closed 8 months ago
Job added to Upwork: https://www.upwork.com/jobs/~014df343518e1f9fe5
Triggered auto assignment to Contributor-plus team member for initial proposal review - @burczu (External
)
Upwork job price has been updated to $250
I would like to work on this
I would love to work on this.
[TS migration] Migrate 'SignInButtons' component to TypeScript
Not problem (Technical ticket )
We need to update these files using best practices using TS guide
https://github.com/Expensify/App/blob/main/contributingGuides/TS_STYLE.md
NA
I would like to work on this. I commented only under this issue
I would like to work on this issue
I would like to work on this issue
I would like to work on this
I would like to work on this issue
I'm available to work on this
SignInButtons
, ReportActionItemFragment
, ReportActionItemMessageEdit
)..ts
extension for each file in the folders.Also, we'd like to mention that it's not good to keep codes for server requests separately https://github.com/Expensify/App/blob/main/src/components/SignInButtons/AppleSignIn/index.ios.js#L12
π£ @Ekaterina-Kaschenko! π£ 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:
Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>
Can I work on this migration?
Contributor details Your Expensify account email: anudeep0306@gmail.com Upwork Profile Link: https://www.upwork.com/freelancers/~019df89cc58fc54b33
To proceed with the TypeScript migration, follow these steps:
Start by updating the file extensions from .js
to .ts
or .tsx
for React components in the following files and directories:
src/components/SignInButtons/IconButton.ts
src/components/SignInButtons/GetUserLanguage.ts
src/components/SignInButtons/GoogleSignIn/index.website.ts
src/components/SignInButtons/GoogleSignIn/index.native.ts
src/components/SignInButtons/GoogleSignIn/index.desktop.ts
src/components/SignInButtons/AppleSignIn/index.website.ts
src/components/SignInButtons/AppleSignIn/index.ios.ts
src/components/SignInButtons/AppleSignIn/index.desktop.ts
src/components/SignInButtons/AppleSignIn/index.android.ts
src/components/SignInButtons/AppleAuthWrapper/index.ts
src/components/SignInButtons/AppleAuthWrapper/index.ios.ts
For each file:
types.ts
file in the root of each component directory (SignInButtons, ReportActionItemFragment, ReportActionItemMessageEdit)..ts
extension.@ts-expect-error
temporarily to suppress TypeScript errors if needed, and create separate GitHub issues to resolve these errors later.β Contributor details stored successfully. Thank you for contributing to Expensify!
It looks like @shahinyan11 was first (not assigned or recommended yet to any other TS migration issue) here, so I think we can assign them.
π π π C+ reviewed
Triggered auto assignment to @yuwenmemon, see https://stackoverflow.com/c/expensify/questions/7972 for more details.
@burczu
@MahmudjonToraqulov already has assigned one here
@shahinyan11 Ahh, thanks for pointing this out - you are right. So the next is @HezekielT on the list.
@burczu
@HezekielT also has assigned
@shahinyan11 where? I've just checked all the TS migration issues on the list from Vit on slack
I'm the first one who hasn't been assigned yet
@burczu Here
No, I was the first one who technically explained the steps
@shahinyan11 Hmmm... I wonder what to do in this situation - @HezekielT is not assigned yet, they are only recommended by the C+. But I think they'll be assigned so I think it's safe to omit them here and assign you, @shahinyan11 instead.
@Ekaterina-Kaschenko Unfortunately, in this type of issues, we don't expect any kind of proposal - who comments first, gets the issue.
@burczu I think If HezekielT
is first in somewhere then I should be assigned here .
@shahinyan11 You are already recommended to be assigned here... https://github.com/Expensify/App/issues/31980#issuecomment-1862308120
@burczu hi. you have an intresting approuch here, why are you looking for person who was first instead of one with tech details and proper planing of solution ? Aren't you aming for better quality for your code/project ?
π£ @yaroslav-sydoryk! π£ 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:
Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>
@yaroslav-sydoryk The community was asked to quickly help with TS migration here: https://expensify.slack.com/archives/C01GTK53T8Q/p1702915376952599.
Quote from this slack message:
whoever bid first, they can implement it
@burczu there wasn't information about Slack community. We did all mentioned in the job details
@Ekaterina-Kaschenko Are you read the CONTRIBUTING.md . I suggest you to read this guide before submitting any proposal
@shahinyan11 @burczu my bad, thank you
π£ @shahinyan11 π An offer has been automatically sent to your Upwork account for the Contributor role π Thanks for contributing to the Expensify app!
Offer link Upwork job Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review π§βπ» Keep in mind: Code of Conduct | Contributing π
I expect my review request to be ready for review by the end of tomorrow.
Hey @yuwenmemon! I'll be OOO till January 6th, and right after that I'm leaving the C+ role and joining Waves. Could you assign another C+ engineer to handle this issue from now on? Thanks.
Triggered auto assignment to Contributor-plus team member for initial proposal review - @rushatgabhane (External
)
Sure thing! @rushatgabhane can you take a look?
Triggered auto assignment to @NicMendonca (NewFeature
), see https://stackoverflowteams.com/c/expensify/questions/14418#:~:text=BugZero%20process%20steps%20for%20feature%20requests for more details.
Reviewing
label has been removed, please complete the "BugZero Checklist".
The solution for this issue has been :rocket: deployed to production :rocket: in version 1.4.24-8 and is now subject to a 7-day regression period :calendar:. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2024-01-22. :confetti_ball:
For reference, here are some details about the assignees on this issue:
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:
TS migration. No regression steps needed.
@NicMendonca could you please add payment summary so it'll be paid on 22nd. Thank you π
BZ Summary: C: @shahinyan11 - $250 (paid via Upwork) C+: @rushatgabhane - $250 (paid via Expensify)
@shahinyan11 you've been paid! @rushatgabhane don't forget to request payment!
$250 payment approved for @rushatgabhane based on summary above.
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
Upwork Automation - Do Not Edit