You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now only game results are published to RabbitMQ, but since the league service doesn't want to duplicate the rater logic, what it really wants is an event published on rating change.
The expected format of these messages is e.g. available in these tests.
When this is done the routing keys in the league service should be updated accordingly.
(Right now the league service actually listens for game results using the "success.gameResult.create" routing key, but it then tries to parse the message as if it was an event as described above and hence fails.)
The text was updated successfully, but these errors were encountered:
Right now only game results are published to RabbitMQ, but since the league service doesn't want to duplicate the rater logic, what it really wants is an event published on rating change.
The expected format of these messages is e.g. available in these tests.
When this is done the routing keys in the league service should be updated accordingly.
(Right now the league service actually listens for game results using the "success.gameResult.create" routing key, but it then tries to parse the message as if it was an event as described above and hence fails.)
The text was updated successfully, but these errors were encountered: