You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great if their was an event emitted for the context ready with its _uid and data. That way the information could be stashed off in a database, file, or somewhere for postmortem efforts.
EG: I know I have a bad account in a list of accounts, but the only way to find it right now is to go look at each one manually till I find the wrong one. With the context's could look at the context request, align it to the uid in the errors and poof I now have something to look at.
The text was updated successfully, but these errors were encountered:
Good suggestion. This is too low-level to be useful to all but the most power of users so I'll create an issue in the main repo to discuss how postmortem analysis / reporting of requests that are causing 404s / 500s etc could work.
It would be great if their was an event emitted for the context ready with its _uid and data. That way the information could be stashed off in a database, file, or somewhere for postmortem efforts.
EG: I know I have a bad account in a list of accounts, but the only way to find it right now is to go look at each one manually till I find the wrong one. With the context's could look at the context request, align it to the uid in the errors and poof I now have something to look at.
The text was updated successfully, but these errors were encountered: