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
When things error - e.g rpc call, need to capture exception and return useful response rather than crashing the app. Currently this is open for individual VUU app developer and every function to implement
Could we have more centralize solution for error handling - for example have one around every RPC call?
Additional Context:
If we want rpc implementor to customise the error message,, could use something like a result pattern (Either in Scala) which returns a success and error result that are of different types
The text was updated successfully, but these errors were encountered:
Might be best to wait for new RPC message type & RPC handler implementation on server side
Related Discussion #1447
Being tackled as part of this change #1434
New RPC response will have standard way to report error & more extendable format
New RPC handler implementation may already handle any error during RPC handling - see if more error/edge case handling is required
May want to introduce event based message to report back server side errors that are not in response to request - e.g. auth token validation failures/ expiry, connection being dropped
Bug Report
Steps to Reproduce:
When things error - e.g rpc call, need to capture exception and return useful response rather than crashing the app. Currently this is open for individual VUU app developer and every function to implement
Could we have more centralize solution for error handling - for example have one around every RPC call?
Additional Context:
If we want rpc implementor to customise the error message,, could use something like a result pattern (Either in Scala) which returns a success and error result that are of different types
The text was updated successfully, but these errors were encountered: