Add basename and parent_folders fields to Folder graphql interface #6494
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.
Preparation work for a folder filter.
basenamefield to theFoldertype. This field is derived from thepathfield - more on this below.parent_foldersfield to theFoldertype, this provides a list of all parent folders for the applicable folder, with the first being the immediate parent and the last being the highest level folder. This means that you can get the full hierarchy of folders (and their ids) with a single query.basenamecolumn. This is necessary for searching folders, since if you search forfooin the path, you will not only get the/foodirectory but all of its subdirectories, sincefoois part of the path. Thebasenamecolumn is automatically calculated from thepathfield during creates and updates.basenamefield to theFolderFilterTypeinput, to allow filtering onbasename.