-
Notifications
You must be signed in to change notification settings - Fork 42
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
feat: various fixes and improvements to schemas #264
Conversation
c29bcd4
to
debed86
Compare
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.
Wow these changes look great!
Sets it to either `string`, `null` or both depending on the event
Sets it to either `enum` or `null` depending on the event type
…oved` payload example
debed86
to
534feef
Compare
Removes the `changes` property from non-`edit` event actions and completes the properties with information from the docs
534feef
to
545e3a1
Compare
This way we can set the repository as private, archived or unarchived, all depending on the event
In some events, properties are set to one boolean value but not the other, for example when the `issue.locked` event is sent, the `locked` property will be set to `false`.
545e3a1
to
3448a4f
Compare
@G-Rath If you could review this as well. I've done a lot of changes, just want you to confirm everything will work as intended especially once they get converted to TS types |
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.
This is A-W-E-S-O-M-E! I'm super excited about all the power these changes landing to webhooks. Congrats to everybody 😍
Sure thing - I'll try to get to sometime this week (works a bit busy right now, so might have to wait a couple of days) |
The openapi spec for the rest api shares a lot of properties with these shemas. |
Agree on that. Should we create an issue to follow up this? |
Yes, for sure. |
Uses `null` for `star.deleted` and `string` for `star.created`
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.
Overall looks good.
I'll need to do some checking on how the enum: [true]
and allOf
s come out, but I don't think they'll be any real trouble.
There are a few optimizations you can make, but I've started committing my optimize-schema
script which'll handle them automatically.
I'm happy if you want to merge this :)
I'm noticing a lot of events have missing schemas & payload examples for the different actions |
49783ff
to
dcf30bf
Compare
🎉 This PR is included in version 3.33.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Should we create an issue for this? Would have sense to tackle it in #266? @wolfy1339 @G-Rath |
No description provided.