-
Notifications
You must be signed in to change notification settings - Fork 325
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
[WPB-4928] Stop using Servant client to enqueue federation notifications #3647
Conversation
808050d
to
9aadc6e
Compare
9e7288d
to
210d643
Compare
210d643
to
0ee2a6d
Compare
0ee2a6d
to
fbc0ea1
Compare
m ~ FedQueueClient comp | ||
forall tag api. | ||
( HasNotificationEndpoint tag, | ||
-- api ~ NotificationAPI tag (NotificationComponent tag), |
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.
When I include this constraint, I get an error about the non-injectivity of a type family and I don't know how to fix it.
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.
LGTM overall, but I don't know about the non-injectivity error either.
This stops using the Servant client to enqueue federation notifications. It also reorganises the federation API notification endpoints such that they are separated more from the synchronous endpoints. The notification endpoints rely on a type alias that always has
EmptyResponse
as the response type.Tracked by https://wearezeta.atlassian.net/browse/WPB-4928.
Checklist
changelog.d