stanza: rewrite Error API #371

Open
opened 2023-03-04 15:38:33 +00:00 by SamWhited · 0 comments

Right now the stanza.Error type uses a custom unmarshaler and consumes the entire error. This makes it impossible to get out application specific error conditions, ie. if you're using pubsub you can't figure out what the specific pubsub error was.

We need to re-write the error type and come up with an error API for getting specific error conditions out or creating new types that can be used to unmarshal specific errors.

I'm at a bit of a loss on how to do this in a nice way, so suggestions would be very welcome.

Right now the `stanza.Error` type uses a custom unmarshaler and consumes the entire error. This makes it impossible to get out application specific error conditions, ie. if you're using pubsub you can't figure out what the specific pubsub error was. We need to re-write the error type and come up with an error API for getting specific error conditions out or creating new types that can be used to unmarshal specific errors. I'm at a bit of a loss on how to do this in a nice way, so suggestions would be very welcome.
SamWhited added this to the omemo milestone 2023-03-04 15:38:33 +00:00
SamWhited added the
enhancement
help wanted
labels 2023-03-04 15:38:34 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: mellium/xmpp#371
There is no content yet.