-
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-12-20] [$250][Cleanup] Always use constants for screen names #32141
Comments
Marking this as external but not help wanted as @blazejkustra is going to work on this. |
Job added to Upwork: https://www.upwork.com/jobs/~01fe00e0d9ee39b022 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @cubuspl42 ( |
Triggered auto assignment to @puneetlath ( |
Upwork job price has been updated to $250 |
Adjusting the C+ review payment for this from $500 to $250 |
Hey! I’m Blazej from Software Mansion, an expert agency, and I’d like to work on this issue! |
📣 @cubuspl42 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app! |
@cubuspl42 @roryabraham PR is ready for review, I didn't post a proposal as this was pretty straight forward change. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.11-25 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-12-20. 🎊 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:
|
This comment was marked as off-topic.
This comment was marked as off-topic.
@puneetlath Do we need to assign someone to process the payment? |
Whoops, I got it. All paid! |
Coming from #31543 (comment)...
Problem
We have two patterns for adding screens in E/App, and we aren't consistent about when a constant should be used for a screen name in
SCREENS.ts
or not. This leads to unnecessary confusion and inconsistency. The developer has to decide which pattern to follow, and if a constant needs to be added must adjust the navigation stack accordingly in a PR that does not add a new screen.Solution
Let's clean this up to always use constants for screen names in E/App (from
SCREENS.ts
).Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: