-
Notifications
You must be signed in to change notification settings - Fork 5.9k
Implement last opened functionality #4633
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
7b27250
to
92865f2
Compare
Codecov Report
@@ Coverage Diff @@
## main #4633 +/- ##
==========================================
- Coverage 66.10% 65.68% -0.42%
==========================================
Files 30 30
Lines 1658 1670 +12
Branches 337 343 +6
==========================================
+ Hits 1096 1097 +1
- Misses 477 486 +9
- Partials 85 87 +2
Continue to review full report at Codecov.
|
This suppresses all the error and debug output we generate which makes it hard to actually find which test has failed. It also gives us a standard way to test logging for the few places we do that.
Exactly as we do for the e2e tests.
2f3a670
to
3bdad9f
Compare
Without this test instances step on each other feet and they also clobber your own non-test settings.
3bdad9f
to
6860c7b
Compare
Testing this took a bit of doing since I wanted to use the integration tests as it uses both the It was hard to see test failures among all the logger output so I added a logger mock and used that everywhere to get rid of the noise. As I was doing that I noticed some accumulating test dirs so I took care of those. I had issues with the settings from the tests stepping all over each other and conflicting with my own running instance of code-server so I had to add some separation to the instances which meant making the settings class use the path provided on the command line. I also added some tests to make sure relative paths are being generated correctly. |
They will preserve the trailing slash if there is one.
681a50d
to
055d27a
Compare
If you do a regular non-watch build there are no compilation stats so this bricks VS Code in CI when running the unit tests. I am not sure how best to fix this for the case where you have a build that has not been packaged yet so I just removed it for now and added a message to check if VS Code is compiling when in dev mode.
055d27a
to
2a08ee5
Compare
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.
LGTM! Nice cleanup 👏
Approving but make sure you look at the URL provided to the Updater
. I think it should use the new GitHub org
Co-authored-by: Joe Previte <[email protected]>
Fixes #4619
This also restores the settings query file write which we were missing.