FileusageGenerator #87
Merged
Conversation
This file contains 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
CXuesong
requested changes
May 24, 2021
CXuesong
approved these changes
May 24, 2021
|
@User123698745 just for confirmation, I'm going to merge without squashing, so your 3 commits in this PR will present in the master branch history. Please raise up if there is any problem for you (such as you are not using the GitHub associated e-mail address to make the commits). |
|
no problems. you can merge it |
This pull request was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
TranscludedInGenerator can not be used for files.
This PR adds FileusageGenerator (API docs) which is basically the same as the TranscludedInGenerator (API docs) just for files.
Note: The API endpoint is called "Imageusage", but it works with any file (see test case).