Exposing pubSub through services and resolvers

[tripss]

Exposing pubSub through services and resolvers

[TriPSs]

I think the JSON.stringify(authorizationFilter) is added to make sure that if you subscribe with certain auth filters you will only get back the events that have the same ones.

The functions like publishUpdatedOneEvent are available to be used right? Think as a starting point it's a good idea to add those to the documentation for better visibility.

[nxmad]

@TriPSs authorizationFilter is lost for deleteOne mutation. When you subscribe to channel, it contains just event name without filters, however event is published to another channel with authfilter, so you will never get event from subscription. Please let me know if you fixed this behaviour in your fork. Or do you have any list of fixes you did?

[TriPSs]

Think this ticket was solved with #64