Fix ResponderRequest unmarshalling of IncidentResponders #493
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes an unmarshalling bug that was found while trying to use the
ResponderRequestWithContext
method on the client.The response that the API returns is subtly different to the one which the client library is expecting. Within the
responder_request_target
object, the client library expects a key calledincident_responders
. However when interacting with the API directly, this key is actuallyincidents_responders
. Note the additionals
which pluralises 'incident'.Impact
This meant that whenever you made a responder request via the client library, it would succeed but the response would only be partial. That meant you could not retrieve any of the information about the responders which your request had added to an incident.
A note on API documentation
Please note that there is an inconsistency in the PagerDuty API documentation for this endpoint.
incident_responders
incidents_responders