-
Notifications
You must be signed in to change notification settings - Fork 3.4k
refactor: remove @packages/desktop-gui #19127
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
refactor: remove @packages/desktop-gui #19127
Conversation
Thanks for taking the time to open a PR!
|
Test summaryRun details
View run in Cypress Dashboard ➡️ Flakiness
This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard |
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.
RIP desktop gui
I agree now is a good time to start aggressively
ereoving old code!
* 10.0-release: refactor: remove @packages/desktop-gui (#19127) feat: switch browser runner (#19048) fix: bump resource class for tests that require node_modules install (#19079) fix(unify): reporter styles (#19034) fix test feat(unify): add number of matches to specs search (#19076) feat(launchpad): open in IDE modal and feature (#18975) fix: 10.0 appveyor updateyaml (#19074)
@packages/desktop-gui
events.ts
which we still might want to reference while building out the data-context layerWhile working on the new codepaths, particularly around config management, I found a number of situations where we were working around legacy concepts in tests which were only referenced from the current
desktop-gui
. By going through and auditing the code-usage from this API layer, and removing all associated code, it reduces the surface area of the code significantly and thus means we can make changes without needing to worry about tests/code that doesn't matter. It also makes it more apparent what still needs to be added in the new codepaths.If we need to reference any of this code, we can find it in
develop
/ in the git history.