2 ms·
yes, thinking about that. Actually, an API bug report should be: 1/ secured, the credentials should not be exposed. 2/ enough information, e.g. the response m
by _thinx 4y ago
yes, thinking about that. Actually, an API bug report should be:
1/ secured, the credentials should not be exposed.
2/ enough information, e.g. the response must be snapshot, general parameters should be transparent.
3/ easy to re-produce and confirm resolved.
What do you think?
- ndimares 4y agoIt makes sense. I think one of the challenges is the question of how much you need to store in order to be able to do this. Hanging onto every request/response object / parameters for an interaction with an API can be become expensive pretty quickly. This becomes an issue when you start thinking about what is considered to be a bug. If you're just talking about error codes, then you're probably fine to store everything. But when you talk about unexplained (but not erroneous) behaviour from the API, how much you need to store to catch the bugs is an important consideration.
- _thinx 4y agoAgree! That's why I think a centralize tracing system is too expensive. Still looking for a better way to send API bug report.