-
Notifications
You must be signed in to change notification settings - Fork 5.3k
Shared physical file provider with base directory as root #63538
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
Closed
mapogolions
wants to merge
2
commits into
dotnet:main
from
mapogolions:shared-physical-file-provider-with-base-directory-as-root
Closed
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
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.
I'm not certain this is a valid change. Thinking about #63540, the
PhysicalFileProviderisIDisposable. Sticking it in thebuilder.Propertiesmeans people may be able to get at it after it has been disposed.Can you add a reasoning/scenario (maybe in an issue?) for why this change is necessary?
Uh oh!
There was an error while loading. Please reload this page.
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.
As I understand from code, the
Propertiesfield of theIConfigurationBuilderinstance is used like a temporary bag to store some shared data that can be used during construction theIConfiguration. Sticking thePhysicalFileProviderin thePropertiesof theConfigurationBuilderalso happens in case when we use another extension method theSetBasePath. Could you please explain to me what the difference between these cases? I just thought it would be great to create and use only onePhysicalFileProviderAt the moment, each configuration source calls
EnsureDefaultsand create own file provider with base directory as root. If we create shared physical file provider then lines of code below will have the same semanticThere 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.
The difference is that calling
SetBasePathis an explicit action to stick the file provider into thePropertiescollection. You can use a singleIConfigurationBuilderto build multiple configurations.If someone disposed the
PhysicalFileProviderwhile it was being held on to theICollectionBuilder, you can get anObjectDisposedExceptionif you tried using theICollectionBuilderagain. It should be an explicit action to cache the file provider into theICollectionBuilder.