Parse uPNP XML errors
Open
enhancement
- Dominant language
- Erlang
- Stars
- 65
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
There's a lot of helpful information in the XML errors we get back from upnp servers:
```
s:ClientUPnPError714NoSuchEntryInArray
```
```
s:ClientUPnPError718ConflictInMappingEntry
```
It would be nice to have some richer errors returned to the user so the client can make better decisions about what it should do.
Contributor guide
No contributing guide indexed for this repository
Research direction
Search the repository for the UPnP SOAP fault handling and compare it with the sample XML responses in this issue. Determine how errorCode and errorDescription should be exposed to clients, then verify that those details are returned for the shown error cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- erlang
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100