-
Notifications
You must be signed in to change notification settings - Fork 20
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
Investigating on Webhook and User types #296
Comments
following ^ ... |
Hello there! |
Thanks a lot @berezovskycom , I will keep an eye on it |
hello everyone, for your information, versions moved from ^8.0.0-beta.32 to ^8.0.0-beta.36 and still I've this problem, |
I could also try to write a PR, in case, do I need an |
any news about this issue? I worked on a small update #305 to solve the Webhook type. I was wondering if that could be merged, or if there is some error to fix. Thanks a lot for the attention |
Hello everyone, I'm working with Abstract API version ^8.0.0-beta.32 and I am checking the Webhook and User types described in file https://github.com/goabstract/abstract-sdk/blob/master/abstract-sdk.d.ts
I setup a small application -built in typescript- with a server listening to the events
branch.statusUpdated
within my project within Abstract.And indeed it works, every time someone merge a branch the event is listened by the server.
Issue is, I would like to use the type you offer, and I thought that
Webhook
type should have been the proper one.But the data I receive in the server is this one
as you might notice from the Webhook type is missing
data
andobject
,event
is notevents
so I guess this won't be the proper one - but I couldn't even find the proper type.What is the Abstract
Webhook
type used for? Shall we expect a properWebhook
type, in line with the data received by the server?Same question for User type that is missing
objectType
.What is the Abstract
User
type used for? Shall we expect a properUser
type, in line with the data received by the server?Thanks
The text was updated successfully, but these errors were encountered: