-
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
[Refactor][QBO] Handle better translation keys #41248
Comments
Triggered auto assignment to @isabelastisser ( |
Job added to Upwork: https://www.upwork.com/jobs/~01065d2b3f47c96271 |
Triggered auto assignment to Contributor Plus for review of internal employee PR - @jayeshmangwani ( |
Current assignee @isabelastisser is eligible for the NewFeature assigner, not assigning anyone new. |
|
Triggered auto assignment to Design team member for new feature review - @shawnborton ( |
Sorry, removing everyone, this is not a |
No updates yet, focusing on helping with the fire |
sames as before |
sames as before |
sames as before |
Coming back from being OOO, I'll try to put some time on this this week. |
No progress yet |
No progress yet |
The function translateIfPhraseKey doesn't exist anymore. I search for something similar in our code and didn't find. I looked into the I'm ok with the current design and using |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number:
Reproducible in staging?:
Reproducible in production?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by:
Slack conversation:
@luacmartins suggested to use translateIfPhraseKey for stages
Context: https://expensify.slack.com/archives/C03TQ48KC/p1714421484252409?thread_ts=1714421087.411779&cid=C03TQ48KC
Action Performed:
N/A
Expected Result:
N/A
Actual Result:
N/A
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: