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

Fixing structs within user.go #72

Merged
merged 1 commit into from
Aug 13, 2019

Conversation

domdoescode
Copy link

  • Add explicit JSON for ContactMethod:
    • ID
    • Label
    • Address
    • Type
  • Add field for ContactMethod:
    • Summary
  • Add explicit JSON for NotificationRule:
    • ID
    • Urgency
    • Type
  • Add explicit JSON for User:
    • InvitationSent
  • Correct explicit JSON for User:
    • timezone to time_zone

The above can be demonstrated by using the user list CLI command on master, and subsequently on this branch.

* Add explicit JSON for `ContactMethod`:
  * `ID`
  * `Label`
  * `Address`
  * `Type`
* Add field for `ContactMethod`:
  * `Summary`
* Add explicit JSON for `NotificationRule`:
  * `ID`
  * `Urgency`
  * `Type`
* Add explicit JSON for `User`:
  * `InvitationSent`
* Correct explicit JSON for `User`:
  * `timezone` to `time_zone`
* Add fields for `User`:
  * `Type`
  * `Summary`
@celestedrobinson
Copy link

I've noticed a similar problem with structs defined in incident.go and have created a similar pull request: #93.

rtilder pushed a commit to rtilder/go-pagerduty that referenced this pull request Feb 27, 2018
Fixing structs within user.go
PagerDuty#72
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 e29882a into PagerDuty:master Aug 13, 2019
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.

3 participants