Update props-system-storageproviderstatus.md #1988
Open
Conversation
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
The string is wrong, it should be StorageProviderState rather than StorageProviderStatus.
Contributor
|
@woojou : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
Contributor
|
Hi @woojou. Both StorageProviderStatus and StorageProviderState exist. I checked the source code, and System.StorageProviderStatus has propID 110, so the existing documentation is correct. System.StorageProviderState has propID of 3. I will check why we don't have a page for StorageProviderState. |
alvinashcraft
requested review from
alvinashcraft
and removed request for
jwmsft
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
The string is wrong, it should be StorageProviderState rather than StorageProviderStatus.
After using the correct string, RetrievePropertiesAsync can return right values. Otherwise, it keeps returning 0 despite of the real status of files.