Part of #76750
Problem
LockAccount needs to send Onyx error data in the following format:
domainErrors_<domainAccountID>?.memberErrors?.[<domainMemberAccountID>]?.lockAccountDetailsErrors
Currently, we don't have logic to send errors under the domainErrors_ Onyx key for the LockAccount endpoints. It only returns errors to account.lockAccount.errors
Solution
- Accept an optional
domainAccountID parameter, since these endpoints are also used elsewhere
- Add BE logic to send errors under the
domainErrors_ Onyx key
Conversation: https://expensify.slack.com/archives/C0A1VKRKEE9/p1770217693513659?thread_ts=1770206258.446149&cid=C0A1VKRKEE9
Doc: https://docs.google.com/document/d/13ZgHapzyeDYny155suwlSRQUvdWqE1DkNNDRJ6Pk3i0/edit?tab=t.0#bookmark=id.h64b4i1dmhf6
Part of #76750
Problem
LockAccountneeds to send Onyx error data in the following format:domainErrors_<domainAccountID>?.memberErrors?.[<domainMemberAccountID>]?.lockAccountDetailsErrorsCurrently, we don't have logic to send errors under the
domainErrors_Onyx key for theLockAccountendpoints. It only returns errors toaccount.lockAccount.errorsSolution
domainAccountIDparameter, since these endpoints are also used elsewheredomainErrors_Onyx keyConversation: https://expensify.slack.com/archives/C0A1VKRKEE9/p1770217693513659?thread_ts=1770206258.446149&cid=C0A1VKRKEE9
Doc: https://docs.google.com/document/d/13ZgHapzyeDYny155suwlSRQUvdWqE1DkNNDRJ6Pk3i0/edit?tab=t.0#bookmark=id.h64b4i1dmhf6