-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[HOLD for payment 2024-01-30] [HOLD for payment 2024-01-25] [$250] [TS migration] Migrate 'GetAssistance' page to TypeScript #25179
Comments
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! |
@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. |
Job added to Upwork: https://www.upwork.com/jobs/~01f1b78d822a1c7910 |
Triggered auto assignment to @anmurali ( |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @cubuspl42 ( |
@AnshuAgarwal24 I understand the decision must have been frustrating and I am sorry this wasn't the outcome you expected. I agree with you that by contributing, people improve their skills. However, there was a substantial gap in your TypeScript knowledge that was preventing you from completing the task and debugging basic errors that you encountered. We can always help with one-off problems but since this is a paid task, it doesn't sound reasonable to finish half of the job for you. As we mentioned, we totally encourage you to apply again in the future once you have practiced more and gained some experience with Typescript. As a start, my advice would be to check how @DylanDylann has solved all the problems you encountered in the PR he created and even doing so with some of the other Typescript tasks that many other contributors have created, it is a great learning opportunity. |
@cubuspl42 The PR is ready for review, I will upload IOS video right after running successfully 😄 |
@AnshuAgarwal24 We reached out to you in private, explaining our decision. We made extra effort to be respectful and clear. I'm sorry that that didn't work. Let me be extra clear.
That's what we just did. TypeScript migration is a special category of issues, not using the proposal system. Before assigning, we don't interview or background check Contributors, as that hasn't been needed so far. In this category, we depend on Contributors' honesty and ability to self-estimate their skills. You either weren't honest or highly over-estimated your skills. I consider this thread closed for discussion. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.26-2 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 2024-01-25. 🎊 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:
|
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.29-1 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 2024-01-30. 🎊 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:
|
@anmurali Ready for payment |
@cubuspl42 abd @DylanDylann are both paid |
No, it does not need one, so closing |
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
Issue Owner
Current Issue Owner: @anmuraliThe text was updated successfully, but these errors were encountered: