-
Notifications
You must be signed in to change notification settings - Fork 102
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 support for team notification configurations #1016
Conversation
A fix for the linting error might be kind of weird IMO, but I can do it if any reviewers feel strongly about it (I saw in CONTRIBUTING.md that linting is not strictly required for these to pass; not sure if this would require an ignore to not be noisy in CI). |
Datadog ReportBranch report: ✅ 0 Failed, 1421 Passed, 159 Skipped, 17m 45.78s Total Time |
@@ -34,13 +34,16 @@ func TestNotificationConfigurationList(t *testing.T) { | |||
assert.Contains(t, ncl.Items, ncTest1) | |||
assert.Contains(t, ncl.Items, ncTest2) | |||
|
|||
t.Skip("paging not supported yet in API") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed the skips for these tests. They work even though we don't really support pagination for these endpoints (we cap at 20 notification configurations maximum per subscribable).
Reminder to the contributor that merged this PR: if your changes have added important functionality or fixed a relevant bug, open a follow-up PR to update CHANGELOG.md with a note on your changes. |
Description
This PR adds support for team notification configurations.
External links
Output from tests