-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[$250] Error message displayed as policy instead of workspace #51930
Comments
Triggered auto assignment to @garrettmknight ( |
Job added to Upwork: https://www.upwork.com/jobs/~021853514819272851093 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @jjcoffee ( |
ProposalPlease re-state the problem that we are trying to solve in this issueError message displayed as What is the root cause of that problem?Note: I was able to reproduce the issue by adding a custom domain (that I own) via OD as instructed in the documentation here -> Claim And Verify A Domain. The error message What changes do you think we should make in order to solve the problem?From what I could gather from the #expensify-bugs Slack discussion seems like the Expected result is:
Therefore the main solution I'm going to propose here is for BE to correct the error message to something like:
What alternative solutions did you explore? (Optional)As an alternative solution (FE based) we could perform a string match of the BE error and if matching
The code would look something like this: Note This is pseudocode-ish, the logic would be adjusted to use In WorkspaceInitialPage.tsx before return add the following logic: const customTranslation = 'Your admin has restricted your group from creating new workspaces.';
const translatedErrors = Object.fromEntries(
Object.entries(policy?.errors ?? {}).map(([key, value]) => [key, value === 'Your admin has restricted your group from creating new policies.' ? customTranslation : value]),
); and the UI: Screen.Recording.2024-11-04.at.17.58.30.mov |
Agree with @ikevin127 that this is a BE issue. We could fix it on the FE for a quick fix if needed, but otherwise this needs to be internal. 🎀👀🎀 C+ reviewed |
Triggered auto assignment to @bondydaa, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
got a pr up here https://github.com/Expensify/Web-Expensify/pull/44298 |
@garrettmknight, @bondydaa, @jjcoffee Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@garrettmknight, @bondydaa, @jjcoffee Huh... This is 4 days overdue. Who can take care of this? |
Will test on Monday. |
@garrettmknight @jjcoffee this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
Fixed - no payments here. |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 9.0.56-7
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?:
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: @quinthar
Slack conversation (hyperlinked to channel name): #expensify-bugs
Action Performed:
Prerequisite:
Expected Result:
Error message displayed regarding restriction for workspace creation
Actual Result:
Error message displayed as
Your admin has restricted your group from creating new policies
Workaround:
Unknown
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
Issue Owner
Current Issue Owner: @garrettmknightThe text was updated successfully, but these errors were encountered: