-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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-08-28] [$1000] [Manual Requests] Refactor usages of action.originalMessage to the transactions key in Onyx #22208
Comments
Triggered auto assignment to @adelekennedy ( |
Triggered auto assignment to Design team member for new feature review - @shawnborton ( |
This is purely a code refactor and doesn't touch any design. So I'm gonna unassign @shawnborton. |
Job added to Upwork: https://www.upwork.com/jobs/~014f38a35df644bdf5 |
Triggered auto assignment to Contributor Plus for review of internal employee PR - @sobitneupane ( |
Hello! I'm from Software Mansion, I'd like to work on this job. |
Current assignee @adelekennedy is eligible for the External assigner, not assigning anyone new. |
Current assignee @sobitneupane is eligible for the External assigner, not assigning anyone new. |
Am I correct and the scope of the task is only |
Hey @kowczarz. No, the scope is the entire App. We want to eventually deprecate originalMessage. |
What docs are you looking for? The data currently found in originalMessage should be available in the new transactions key |
Got a draft PR up. Will finish once the related Edit IOU PR is merged. |
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. |
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. |
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. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.55-8 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 2023-08-28. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
We're over the regression period. I see that nobody requires payment here, so I'm gonna close this issue. Please let me know if I missed something and we need to reopen this issue.
|
@sobitneupane @adelekennedy I think we still need to post the summarizing post for what the payments for Manual requests will be |
double check me @mountiny - only @sobitneupane is due for the internal PR review, is that correct? |
that sounds correct to me |
Payouts due:Contributor+: $500 for internal PR review @sobitneupane. NewDot |
Requested payment on newDot |
$500 approved for payment via NewDot based on BZ summary. |
Problem
We are now storing the transactions key in Onyx and should no longer use
action.originalMessage.<amount|comment|date|etc>
.Why is this important?
Avoids data duplication and keeps the codebase clean and less confusing
Solution
Refactor the code!
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: