Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add comment above IncidentDetails.Alerts field explaining behaviors #335

Merged
merged 1 commit into from
Oct 9, 2021

Conversation

theckman
Copy link
Collaborator

For the Webhook object sent from PagerDuty, the "alerts" key is not a JSON array
of fully hydrated objects. Instead, only the "alert_key" JSON key is set within
each object, which might be unclear based on the type we use in the Go client.

This change adds a comment above the Alerts field to indicate it's not a slice
of fully hydrated IncidentAlert values, and that only AlertKey is set.

@theckman theckman added this to the v1.5.0 milestone May 18, 2021
Copy link
Contributor

@stmcallister stmcallister left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! Thanks! 🎉 🌮 👍

For the Webhook object sent from PagerDuty, the "alerts" key is not a JSON array
of fully hydrated objects. Instead, only the "alert_key" JSON key is set within
each object, which might be unclear based on the type we use in the Go client.

This change adds a comment above the Alerts field to indicate it's not a slice
of fully hydrated `IncidentAlert` values, and that only `AlertKey` is set.
@theckman theckman merged commit b7286a4 into master Oct 9, 2021
@theckman theckman deleted the clarify_webhook_alert branch October 9, 2021 21:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants