Feature/1078 asset indexing improvements #12604
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
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.
Description
Previously, when all files and folders were removed from the FS root folder, asset indexing was bailing before it started. This PR changes this behaviour, so indexing will still go ahead even if the FS root folder is completely empty.
It also introduces the
listEmptyFoldersoption, which, if turned on, will list folders that exist but are empty or could be empty because all files in them are listed as missing and allows you to choose to delete such folders.The review screen now divides into two lists (folders and files) to clarify the messaging in cases where
listEmptyFoldersistrue.Related issues
#12585