-
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 2022-12-08] [$250][Form Refactor] CompanyStep #9580
Comments
Triggered auto assignment to @adelekennedy ( |
@luacmartins is this something contributors can work on? Double checking before I open an Upwork job |
Yes! The Form refactor project is all open to contributors :) |
This issue is being put on hold due to push to page discussions, as per this comment. |
Ty ty! |
on hold |
on hold |
on hold |
@adelekennedy removing hold! We can post this job on upwork and get contributors to start working on it! |
let's gooooo |
PR is almost merged here. |
Working through the commits, but looks like we should be through those really soon, ideally in the coming day or two. |
this is now merged, there were some issue gettin the commits verified, but after creating a new PR this was fixed and everyine was happy |
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. |
there was a deploy blocker associated, but that seems to have been fixed now |
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.2.34-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 2022-12-08. 🎊 After the hold period, please check if any of the following need payment for this issue, and if so check them off after paying:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
@sketchydroide @luacmartins This is supposed to be paid out today, but before that I would like to request a raise for this one. This is was held for a long time for AddressForm, and went through multiple rounds for the review. Compared to average issues, this was a bit bigger. |
@mananjadhav what price do you think is fair? |
pending payment on the discussion above |
I think 500$ should be fine here. Please note this also had a regression involved. So incase we don't want to increase then that is fine too. |
I would go with the first option :) , it's been long back and forth. Thanks, looking forward. |
$500 seems fair to me. Let's go with that. |
Thanks @luacmartins. @adelekennedy can you help with the payout here? |
@mananjadhav just hired you at $500 |
Accepted @adelekennedy |
paid and paid! |
@adelekennedy @mananjadhav I've received only $250. |
Re-opening until the contributor's question is answered. |
Sorry about that @ravindra-encoresky , not sure what happened. I just bonused you $250 so total compensation is now $500. Double checked Manan's contract and the payment was $500 there, re-closing |
Got it, thank you. |
Coming from the New Expensify Forms design doc, we should refactor CompanyStep to use the new form component, follow the guidelines below:
Here's an example of a Form refactor: #9056
Guidelines
Testing
Verify that:
fix the errors
link focuses the first input with errorThe text was updated successfully, but these errors were encountered: