-
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 2023-12-21][$500] Update CONSTS to direct developers to use role instead of accessibilityRole #31500
Comments
Hey @dangrous -- this is my baby! |
📣 @trevor-coleman! 📣
|
As a note: I don't get paid via Upwork as I'm with Infinite Red. |
Job added to Upwork: https://www.upwork.com/jobs/~012561c8136f1b8b5a |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @allroundexperts ( |
📣 @allroundexperts Please request via NewDot manual requests for the Contributor role ($500) |
📣 @allroundexperts Please request via NewDot manual requests for the Reviewer role ($500) |
The BZ member will need to manually hire trevor-coleman for the Contributor role. Please store your Upwork details and apply to our Upwork job so this process is automatic in the future! |
sorry for all the notifications - trying to get a C+ here, (thanks @allroundexperts!), @trevor-coleman will be handling the issue |
Update CONSTS to direct developers to use role instead of accessibilityRole (Expensify#31500)
I've got a draft PR going, but not sure how to handle the testing part. Should I write up tests for every component touched her? It would be quite a few components (~100), and as the changes are a like-for-like substitution of values from a known list of acceptable values I think the risk it pretty low. Happy to do whatever is needed, just wanted to get some advice on what an appropriate testing section looks like for a find-replace PR like this. |
That's a great question. I think if most of the changes are exactly the same, I think we can call out the testing steps for just a few of them. Since this also shouldn't cause any visual change, it shouldn't be too bad. @allroundexperts since you've done a lot more testing, what are your thoughts on the best way forward? |
@trevor-coleman @dangrous what about adding a new lint rule? |
PAYOUT NOTES @dangrous you can close this when needed as @allroundexperts will request his payment via NewDot |
Issue is ready for payment but no BZ is assigned. @peterdbarkerUK you are the lucky winner! Please verify the payment summary looks correct and complete the checklist. Thanks! |
|
@trevor-coleman doesn't need to be paid via UpWork, as he's Infinite Red. @allroundexperts could you send your request via NewDot? @JmillsExpensify is OoO so it might take a week or so to action: $500 for C+ review. |
Weird that this assigned me for the payment issue in addition to @abekkala, maybe due to holiday season OoO? |
@JmillsExpensify $500 to @allroundexperts when it's sent, thanks! |
@JmillsExpensify, @dangrous, @abekkala, @peterdbarkerUK, @trevor-coleman, @allroundexperts Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
@allroundexperts have you requested your payment in New Dot? |
This one is ready to be closed out once: |
@JmillsExpensify, @dangrous, @abekkala, @peterdbarkerUK, @trevor-coleman, @allroundexperts Eep! 4 days overdue now. Issues have feelings too... |
@abekkala I've noted it down. Feel free to close. Thanks! |
@JmillsExpensify, @dangrous, @abekkala, @peterdbarkerUK, @trevor-coleman, @allroundexperts Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it! |
@allroundexperts sorry Sibtain, I'm a bit confused: did you already request and receive this payment? |
@JmillsExpensify, @dangrous, @abekkala, @peterdbarkerUK, @trevor-coleman, @allroundexperts 10 days overdue. Is anyone even seeing these? Hello? |
@peterdbarkerUK I have requested payment but haven't received it yet. I think we can close this issue because receiving the payment does take some time. |
CC @JmillsExpensify this one should be ready to go, $500 to @allroundexperts Let's close once payment is confirmed, no need to risk things slipping through the cracks :) |
This issue has not been updated in over 14 days. @JmillsExpensify, @dangrous, @abekkala, @peterdbarkerUK, @trevor-coleman, @allroundexperts eroding to Weekly issue. |
How are we looking on this one? I think still waiting on payment for @allroundexperts from @JmillsExpensify, is that right? |
yes, that is correct |
I don't think I've received a payment request, though as a heads up, we don't keep issues open that are waiting payment in Expensify. Feel free to close it. |
Ah yeah, I just checked. @allroundexperts needs to submit the report to me, as that's the only way it shows up in my LHN. But again, no need to keep this issue open for Expensify payments, so I'd go ahead and close it. |
sounds good @JmillsExpensify thanks! |
$500 payment to @allroundexperts based on this comment. |
This will encourage appropriate code syntax moving forward and keep things clean and on the cutting edge!
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @JmillsExpensifyThe text was updated successfully, but these errors were encountered: