Closed asaf closed 1 year ago
Name | Link |
---|---|
Latest commit | f29cfe287ed0c14d1da3f7454b222405f206e462 |
Latest deploy log | https://app.netlify.com/sites/crossid/deploys/640077ceacfd3b00083e2efd |
@asaf about the 3rd point,
Showing the correct error requires changing x/writer/WriteError
which I'm reluctant to do.
Many other functions use it and I'm not 100% sure what the repercussions would be.
@asaf about the 3rd point, Showing the correct error requires changing
x/writer/WriteError
which I'm reluctant to do. Many other functions use it and I'm not 100% sure what the repercussions would be.
thanks I was talking about showing some error on the UI side not changing the backend.
This requires a bit more effort:
Transaction aborted. Caught exception during transaction
on the backend, some of them work, we at least should propagate the error message somewhere on the screen.