docs(events): Mathcing data params in server-side plugin-config example with client-side data params of custom events #96
Conversation
This file contains hidden or 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
The server-side code should include ìd` as receivable data along with `name` - this then matches the data entities sent by the client and `id` is also used in the server code. Let me know if I'm wrong, I didn't test it locally.
prithvi2k2
changed the title
prithvi2k2
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The server-side code should include
idas receivable data along withname- this then matches the data entities sent by the client andidwas also used in the server code without prior definition. Let me know if I'm wrong, I didn't test it locally.Description
Added
idparam to custom events example config to match the event proto of clientType of change
Relevant Issue(s)