Dependent keys are not working as expected when using withOnyx

[tgolen]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Action Performed:

1. In EditRequestPage, remove the several withOnyx and join everything in one
2. Add a console.log to check the value of the prop policy
3. Make a money request in a workspace and try to edit the description
4. Check that the policy is always null
5. If you add a console.log to the key callback of the parentReport, the report used will always be undefined.

Expected Result:

The policy and parentReport is populated correctly

Actual Result:

The policy and parentReport are undefined.

Workaround:

This can be worked around by nesting several calls to withOnyx()

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android / native
• Android / Chrome
• iOS / native
• iOS / Safari
• MacOS / Chrome / Safari
• MacOS / Desktop

Version Number: v1.3.72-5
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
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
Issue reported by: @BeeMargarida
Slack conversation:

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~0193a31795e8e571af
• Upwork Job ID: 1704656762098425856
• Last Price Increase: 2023-09-21

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~0193a31795e8e571af

[melvin-bot]

Triggered auto assignment to @greg-schroeder (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[melvin-bot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[melvin-bot]

Triggered auto assignment to Contributor Plus for review of internal employee PR - @allroundexperts (Internal)

[tgolen]

Oops, sorry for removing you @greg-schroeder. I'm working on this as an internal issue and I have a PR for it already that I am working on.

This GH will be used so that @allroundexperts can get paid for helping out with it and @BeeMargarida for reporting it.