-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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-03-18] [TS Migration] Standardize approach to Onyx pendingFields #34662
Comments
dibs |
Hi, I'm Viktoryia from Callstack - expert contributor group - and I would like to work on this issue. |
Sorry @AnshuAgarwal24, this topic was discussed in slack before an issue was created, and we already had an assignment in mind. I would've assigned them right away but because of our GitHub configuration they need to comment first before we can assign them. |
Just answered some questions in the draft PR |
Triggered auto assignment to @puneetlath ( |
@roryabraham Could you help to assign a CME to this issue for payment? |
@puneetlath assigned you back since you have been previously assigned by the NewFeature label I believe this is ready to payout to @DylanDylann for $250 for the review |
Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO. |
@DylanDylann can you link me your Upwork profile? |
@DylanDylann sent you an offer: https://www.upwork.com/nx/wm/offer/101473125 Please ping me on this issue once you've accepted. |
@puneetlath Accepted. Thanks |
Paid, thanks everyone! |
Slack context: https://expensify.slack.com/archives/C0593T50UHG/p1705346773892779
Problem
We do not have a consistent pattern for pendingFields in Onyx, resulting in multiple divergent implementations, greater likelihood of bugs, and developer overhead to choose the "correct" one.
Solution
Standardize our approach to pendingFields in Onyx.
The text was updated successfully, but these errors were encountered: