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

return http code with errors #134

Merged
merged 1 commit into from
Feb 5, 2020

Conversation

yoMashX
Copy link
Contributor

@yoMashX yoMashX commented Jan 14, 2019

A suggested way to return the http codes with errors for events. Some errors are retry-able while others (most) are not, so having that information to callers would be helpful.

https://v2.developer.pagerduty.com/docs/errors

dobs added a commit to dobs/go-pagerduty that referenced this pull request Mar 19, 2019
This branch incorporates a bunch of old un-merged PRs from upstream, specifically:

- PagerDuty#72
- PagerDuty#73
- PagerDuty#74
- PagerDuty#75
- PagerDuty#78
- PagerDuty#91
- PagerDuty#93
- PagerDuty#97
- PagerDuty#104
- PagerDuty#106
- PagerDuty#108
- PagerDuty#113
- PagerDuty#114
- PagerDuty#126
- PagerDuty#127
- PagerDuty#130
- PagerDuty#132
- PagerDuty#137
- PagerDuty#138
- PagerDuty#140
- PagerDuty#143

It doesn't attempt to merge, due to potential complexity:

- PagerDuty#48
- PagerDuty#99
- PagerDuty#134

And skips the following as it was picked up as part of pulling in the above merged PRs:

- PagerDuty#133

Will have subsequent PRs for cleanup, specifically:
- Reducing duplicate code.
- Standardizing response and error handling.

Followed by more janitorial and refactor-oriented changes.
@stmcallister stmcallister merged commit cb8001f into PagerDuty:master Feb 5, 2020
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