We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently web checks a dedicated option to disable the search bar, introduced wcith #3817
However, the capabilities do contain the list of reports that clients can fire against webdav.
For backend search (aka sdk search) the capabilities.dav.reports string array has to contain "search-files":
capabilities.dav.reports
"search-files"
... { "dav":{ "chunking":"", "trashbin":"1.0", "reports": ["search-files"], "chunkingParallelUploadDisabled":false } } ...
Web should rely on that dav.reports property in the capabilities instead of an option in the config.
dav.reports
Another report is a filter-files report which is used to filter files by favorites and tags ... but that is a different issue.
filter-files
The text was updated successfully, but these errors were encountered:
Agreed, capability should have precedence and the config.json option can be dropped immediately.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Currently web checks a dedicated option to disable the search bar, introduced wcith #3817
However, the capabilities do contain the list of reports that clients can fire against webdav.
For backend search (aka sdk search) the
capabilities.dav.reports
string array has to contain"search-files"
:Web should rely on that
dav.reports
property in the capabilities instead of an option in the config.Another report is a
filter-files
report which is used to filter files by favorites and tags ... but that is a different issue.The text was updated successfully, but these errors were encountered: