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
Currently the managed mjolnir is emulating sync by emitting events on the mjolnir's matrix-bot-sdk MatrixClient. This is obviously hacky and will cause problems later on. We also don't have any way to emulate room.join for managed mjolnirs and this is an edge case that must be considered during this refactor.
closes#411.
Issue #411 says that we have to be careful about room.join,
but this was before we figured how to make matrix-appservice-bridge
echo events sent by its own intents.
* Refactor Matrix event listener in Mjolnir and ManagedMjolnir.
closes#411.
Issue #411 says that we have to be careful about room.join,
but this was before we figured how to make matrix-appservice-bridge
echo events sent by its own intents.
* Remove MatrixClientListener since it isn't actually needed.
* Protect which config values can be used for ManagedMjolnirs.
* Introduce MatrixSendClient
so listeners aren't accidentally added to a MatrixClient instead
of MatrixEmitter.
* doc
* Move provisioned mjolnir config to src/config.
This just aids maintance so whenever someone goes to change the config
of the bot they will see this and update it.
* doc for matrix intent listener.
Currently the managed mjolnir is emulating sync by emitting events on the mjolnir's matrix-bot-sdk
MatrixClient
. This is obviously hacky and will cause problems later on. We also don't have any way to emulateroom.join
for managed mjolnirs and this is an edge case that must be considered during this refactor.mjolnir/src/appservice/MjolnirManager.ts
Lines 184 to 199 in 818e4cf
The text was updated successfully, but these errors were encountered: