Skip to content

Remove IFileSystemUtils from IoC container #8898

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

Merged
merged 1 commit into from
Dec 5, 2019

Conversation

DonJayamanne
Copy link

@DonJayamanne DonJayamanne commented Dec 4, 2019

For #8307
Removing IFileSystemUtils from the IOC container as this then means we have 2 ways of accessing FIleSystem related stuff (IFileSystem and IFileSystemUtils).

From what I can tell FileSystemUtils is used purely in fileSystem class and doesn't need to be exposed outside. Hence we shouldn't even need the IFileSystemUtils interface, as the class is sufficient. Though i'm not removing that here as thats a point of preference. There are other similar interfaces as well. Not sure why they exist instead of using pure classes.

This PR ensures we continue to have one way for FS stuff and theres no confusion.

@DonJayamanne DonJayamanne added the no-changelog No news entry required label Dec 4, 2019
@codecov-io
Copy link

codecov-io commented Dec 4, 2019

Codecov Report

Merging #8898 into master will decrease coverage by <.01%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #8898      +/-   ##
==========================================
- Coverage   57.95%   57.94%   -0.01%     
==========================================
  Files         527      527              
  Lines       27532    27530       -2     
  Branches     4146     4146              
==========================================
- Hits        15955    15953       -2     
  Misses      10700    10700              
  Partials      877      877
Impacted Files Coverage Δ
src/client/common/platform/fileSystem.ts 74.77% <ø> (ø) ⬆️
src/client/common/platform/types.ts 100% <ø> (ø) ⬆️
src/client/common/platform/serviceRegistry.ts 100% <100%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 434131a...7d0fe2e. Read the comment docs.

@DonJayamanne DonJayamanne changed the title Remove IFileSystemUtils from IOC container Remove IFileSystemUtils from IoC container Dec 4, 2019
Copy link

@ericsnowcurrently ericsnowcurrently left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for doing this.

@ericsnowcurrently
Copy link

FWIW, My eventual plan was to get rid of IFileSystem (and move everything to IFileSystemUtils). However, until then there certainly is no reason to have IFileSystemUtils in the IOC container. :)

@DonJayamanne DonJayamanne merged commit 8ab93d7 into microsoft:master Dec 5, 2019
ericsnowcurrently added a commit to ericsnowcurrently/vscode-python that referenced this pull request Dec 9, 2019
ericsnowcurrently added a commit that referenced this pull request Dec 10, 2019
(for #8890)

The plan is to un-revert this stuff bit-by-bit.

* Revert "Fixes to FileSystem code to use bitwise operations (#8966)"
This reverts commit acb59d3.

* Revert "Make sure IFileSystem is registered in DI during tests. (#8902)"
This reverts commit dabd87f.

* Revert "Remove IFileSystemUtils from IOC container (#8898)"
This reverts commit 8ab93d7.

* Revert "Skip a few more tests. (#8830)"
This reverts commit d197557.

* Revert "Skip problematic tests. (#8810)"
This reverts commit c5f7766.

* Revert "Use new VS Code filesystem API. (#8307)"
This reverts commit 7cbd1c2.

* Revert "Update the code base to use IFileSystem instead of fs and fs-extra. (#7915)"
This reverts commit a23761d.
@lock lock bot locked as resolved and limited conversation to collaborators Dec 12, 2019
@DonJayamanne DonJayamanne deleted the removeIFileSystemUtils branch December 17, 2019 17:30
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
no-changelog No news entry required
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants