Optional. The map keys of the Aspects which the service should modify. It
supports the following syntaxes:
<aspect_type_reference> - matches an aspect of the given type and empty
path.
<aspect_type_reference>@path - matches an aspect of the given type and
specified path. For example, to attach an aspect to a field that is
specified by the schema aspect, the path should have the format
Schema.<field_name>.
<aspect_type_reference>* - matches aspects of the given type for all
paths.
*@path - matches aspects of all types on the given path.
The service will not remove existing aspects matching the syntax unless
delete_missing_aspects is set to true.
If this field is left empty, the service treats it as specifying
exactly those Aspects present in the request.
Optional. The map keys of the Aspects which the service should modify. It
supports the following syntaxes:
<aspect_type_reference> - matches an aspect of the given type and empty
path.
<aspect_type_reference>@path - matches an aspect of the given type and
specified path. For example, to attach an aspect to a field that is
specified by the schema aspect, the path should have the format
Schema.<field_name>.
<aspect_type_reference>* - matches aspects of the given type for all
paths.
*@path - matches aspects of all types on the given path.
The service will not remove existing aspects matching the syntax unless
delete_missing_aspects is set to true.
If this field is left empty, the service treats it as specifying
exactly those Aspects present in the request.
Optional. The map keys of the Aspects which the service should modify. It
supports the following syntaxes:
<aspect_type_reference> - matches an aspect of the given type and empty
path.
<aspect_type_reference>@path - matches an aspect of the given type and
specified path. For example, to attach an aspect to a field that is
specified by the schema aspect, the path should have the format
Schema.<field_name>.
<aspect_type_reference>* - matches aspects of the given type for all
paths.
*@path - matches aspects of all types on the given path.
The service will not remove existing aspects matching the syntax unless
delete_missing_aspects is set to true.
If this field is left empty, the service treats it as specifying
exactly those Aspects present in the request.
Optional. The map keys of the Aspects which the service should modify. It
supports the following syntaxes:
<aspect_type_reference> - matches an aspect of the given type and empty
path.
<aspect_type_reference>@path - matches an aspect of the given type and
specified path. For example, to attach an aspect to a field that is
specified by the schema aspect, the path should have the format
Schema.<field_name>.
<aspect_type_reference>* - matches aspects of the given type for all
paths.
*@path - matches aspects of all types on the given path.
The service will not remove existing aspects matching the syntax unless
delete_missing_aspects is set to true.
If this field is left empty, the service treats it as specifying
exactly those Aspects present in the request.
Optional. If set to true and the aspect_keys specify aspect ranges, the
service deletes any existing aspects from that range that weren't provided
in the request.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-01-28 UTC."],[],[]]