-
Notifications
You must be signed in to change notification settings - Fork 3.3k
internal: (studio) add socket listeners #31470
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
Conversation
cypress
|
Project |
cypress
|
Branch Review |
mschile/studio/add_socket_listener
|
Run status |
|
Run duration | 14m 16s |
Commit |
|
Committer | Matt Schile |
View all properties for this run ↗︎ |
Test results | |
---|---|
|
0
|
|
1
|
|
10
|
|
0
|
|
585
|
View all changes introduced in this branch ↗︎ |
UI Coverage
0%
|
|
---|---|
|
4
|
|
0
|
Accessibility
97.09%
|
|
---|---|
|
0 critical
1 serious
0 moderate
0 minor
|
|
6
|
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.
Copilot reviewed 7 out of 9 changed files in this pull request and generated no comments.
Files not reviewed (2)
- packages/server/package.json: Language not supported
- packages/types/package.json: Language not supported
Comments suppressed due to low confidence (1)
packages/server/lib/socket-base.ts:410
- [nitpick] Consider adding a test case to verify the behavior when coreData.studio is undefined to ensure addSocketListeners is not called unexpectedly.
getCtx().coreData.studio?.addSocketListeners(socket)
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
Additional details
Updated
socket-base
to calladdSocketListeners
on the studio manager to allow studio to add any necessary socket listeners.Steps to test
n/a
How has the user experience changed?
n/a
PR Tasks
cypress-documentation
?type definitions
?