-
Notifications
You must be signed in to change notification settings - Fork 243
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
ContactMethod field does not populate inside the NotificationRule on a User #250
Comments
@stefprez can you give me an idea of how you're calling |
@stefprez oh sorry, I misread your question originally. That is the expected behavior in terms of how PagerDuty documents their API, and the fact you expected it to be present might indicate a deficiency in our library. Please refer to this API documentation page. You'll notice that under the schema for the response, the The PagerDuty REST API often returns references to the real object instead of returning the whole object in the response. This is to keep response sizes down. I don't believe we should try to make the extra requests on behalf of the consumer to populate that data, so I think this bug should be marked as That said, for |
I've opened that issue and will now close this one in favor of #279 |
Excellent. Thanks for the additional context! |
When fetching a user, the
NotificationRules
get populated for that user, but theContactMethod
field on eachNotificationRule
in the[]NotificationRules
always seems to be empty.The text was updated successfully, but these errors were encountered: