Implement Missing Event Handler StreamSyncedMetaChange on Server #45
+86
−1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
TheDutchDev
force-pushed
the
36-missing-streamsyncedmetachange-eventhandler-server
branch
from
918f3b6 to
b363dda
Compare
TheDutchDev
force-pushed
the
36-missing-streamsyncedmetachange-eventhandler-server
branch
from
b363dda to
c66f2a3
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#36
Followed the SyncedMetaDataChange event and implemented the same for streamsyncedmetadata. I'm guessing I missed something here and there, but no idea how events exactly work internally.
I do assume the event exists within the runtime though since some things like the enum
EventType.STREAM_SYNCED_META_CHANGEalready existed. Although I don't know if this conflicts with the client-side implementation.