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.
feat: setup connection to dynamic parameters websocket #17393
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
feat: setup connection to dynamic parameters websocket #17393
Changes from 1 commit
7b61485
f5d4a1c
0fc4289
d109874
7c13eb7
4290284
74084fb
05adc15
b2c662a
2da7d99
98dfee2
d1ada89
e04ce2f
a6f480d
2613100
1e66a71
9a9201e
1777ca9
440fedc
4f056af
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
one last thought, I noticed that
onMessage
is wrapped in auseCallback
but this isn't. was that intentional? could be nice to wrap this one as well since it's also being passed as a prop to a child 🤷♀️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.
onMessage was wrapped because its used as a dependency for a useEffect. Sure I can wrap sendMessage as well.