HTTP signatures
Standard message payloads
Descriptive error messages
3 comments
Just this: there are tons of ways that an API call can fail, but most Fediverse software just returns something unhelpful, like 500 Internal Server Error. For production software, thatβs probably reasonable, but a well-written test suite should help people debug, not just tell them about the bug. So if I have a voice, a test suite should really return errors like: βthis message was not accepted because it is missing a βnameβ field.β @benpate @activitypubtestsuite Right! Somewhere between returning error message payload in HTTP error responses, or logging things to the app's log or the system log, if it is reasonably easy to get at ... I agree! |
@benpate @activitypubtestsuite "Descriptive error messages" is a new one for me. Give an example?