Webhooks / Subscription in Mock about ngitlab

[meziantou]

NGitLab.Mock doesn't support webhooks. However, based on your needs, you can use the events on collections to detect when a change occurs (INotifyCollectionChanged).

[meziantou]

I'm not sure what it would take to support webhooks in tests. Feel free to share some ideas :)

[mvarendorff]

The collection notifier is very close to what I need actually! If there was something like this to listen for the items in the collection to change, that would be immensely useful. So that I could listen for calls to, for instance, gitLab.Issues.EditAsync; the collection notifier does allow listening for gitLab.Issues.CreateAsync though!

I am unsure how that would look like in code but given some guidance I could look into making a PR!

[meziantou]

Implementing something that would allow simulating webhooks is more complicated as webhooks, most of the time, has the previous and new values. So, you can't only rely on IPropertyChanged / INotifyCollectionChanged.

I forgot to mention the Server.ClientOperation event that is raised for each method on a client. The event is currently empty, so you don't know which method is called, but we could add more data to it if needed.

[mvarendorff]

What you mentioned about requiring the previous values definitely is true; we make lots of use of that to check in what ways the assignee or labels for example have changed to react to that accordingly.

Yeah, I saw Server.ClientOperation but couldn't find much use in the empty args indeed. What information would go in there? The way it's currently being invoked makes it quite difficult to pass any result-y sort of thing because the scope is always created before any action happens.