[FEATURE] Return more fine-grained errors from WADM handlers

[joonas]

Is your feature request related to a problem? Please describe.

A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Currently handlers respond with a single type of error ("result": "error"), which makes it tedious to handle errors on the client-side when calling in.

Describe the solution you'd like

It would be fantastic, if each of the wadm handlers had a set of errors that represented the different scenarios that might go wrong or validations on wadm's side which it could then return to the caller. This would make it easier to handle error results from wadm in a more graceful and intelligent fashion.

Describe alternatives you've considered

None.

Additional context

None.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this has been closed too eagerly, please feel free to tag a maintainer so we can keep working on the issue. Thank you for contributing to wasmCloud!

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this has been closed too eagerly, please feel free to tag a maintainer so we can keep working on the issue. Thank you for contributing to wasmCloud!

[joonas]

This isn't stale 🙂

[brooksmtownsend]

@joonas Do you think this is resolved with the wadm-client crate and the inclusion of a ClientError? Or is there more detail you'd like to have here https://docs.rs/wadm-client/0.3.0/wadm_client/error/enum.ClientError.html

[joonas]

@joonas Do you think this is resolved with the wadm-client crate and the inclusion of a ClientError? Or is there more detail you'd like to have here https://docs.rs/wadm-client/0.3.0/wadm_client/error/enum.ClientError.html

Yep, I think that's a great starting point that we can expand upon as new cases crop up, going to close this out.