search method
Search for folders that match specific filter criteria.
search()
provides an eventually consistent view of the folders a user
has access to which meet the specified filter criteria. This will only
return folders on which the caller has the permission
resourcemanager.folders.get
.
Request parameters:
pageSize
- Optional. The maximum number of folders to return in the
response. The server can return fewer folders than requested. If
unspecified, server picks an appropriate default.
pageToken
- Optional. A pagination token returned from a previous call
to SearchFolders
that indicates from where search should continue.
query
- Optional. Search criteria used to select the folders to return.
If no search criteria is specified then all accessible folders will be
returned. Query expressions can be used to restrict results based upon
displayName, state and parent, where the operators =
(:
) NOT
, AND
and OR
can be used along with the suffix wildcard symbol *
. The
displayName
field in a query expression should use escaped quotes for
values that include whitespace to prevent unexpected behavior. | Field | Description | |-------------------------|----------------------------------------| | displayName | Filters by displayName. | | parent | Filters by parent (for example: folders/123). | | state, lifecycleState | Filters by state. |
Some example queries are: * Query displayName=Test*
returns Folder
resources whose display name starts with "Test". * Query state=ACTIVE
returns Folder resources with state
set to ACTIVE
. * Query
parent=folders/123
returns Folder resources that have folders/123
as a
parent resource. * Query parent=folders/123 AND state=ACTIVE
returns
active Folder resources that have folders/123
as a parent resource. *
Query displayName=\\"Test String\\"
returns Folder resources with
display names that include both "Test" and "String".
$fields
- Selector specifying which fields to include in a partial
response.
Completes with a SearchFoldersResponse.
Completes with a commons.ApiRequestError if the API endpoint returned an error.
If the used http.Client
completes with an error when making a REST call,
this method will complete with the same error.
Implementation
async.Future<SearchFoldersResponse> search({
core.int? pageSize,
core.String? pageToken,
core.String? query,
core.String? $fields,
}) async {
final queryParams_ = <core.String, core.List<core.String>>{
if (pageSize != null) 'pageSize': ['${pageSize}'],
if (pageToken != null) 'pageToken': [pageToken],
if (query != null) 'query': [query],
if ($fields != null) 'fields': [$fields],
};
const url_ = 'v3/folders:search';
final response_ = await _requester.request(
url_,
'GET',
queryParams: queryParams_,
);
return SearchFoldersResponse.fromJson(
response_ as core.Map<core.String, core.dynamic>);
}