template <typename BuilderImpl>class WireTableBaseBuilder
Defined at line 2899 of file fidling/gen/sdk/fidl/fuchsia.feedback/fuchsia.feedback/cpp/fidl/fuchsia.feedback/cpp/wire_types.h
Public Methods
::fuchsia_feedback::wire::ComponentData Build ()Build and return the table. The builder should not be used after this.
bool has_namespace ()void clear_namespace ()Clears the namespace_ field.
This method should be used sparingly, such as only during tests, as it has
O(number_of_fields) complexity.
::fidl::StringView & namespace_ ()The top-level namespace associated with the data:
* Is intended to group related data together and reduce data key collisions across
namespaces.
* May be shared by multiple clients, e.g., there could be multiple clients within the same
component or across components that want to expose related data and they would all use
the same namespace.
* Will be prefixed to every data key passed within that namespace in all feedback reports,
e.g., the annotation "version" would appear as "foo.version" in all feedback reports if
the namespace is "foo".
* Must match [a-z
\
-]+, i.e. only lowercase letters and hyphens or this will result in a
ZX_ERR_INVALID_ARGS epitaph.
* Must not match a reserved namespace used internally for platform data, e.g., "build", or
this will result in a ZX_ERR_INVALID_ARGS epitaph. The list of reserved namespaces is
internal and subject to change for now.
BuilderImpl & namespace_ (Wrapper_Ignore_Me_< ::fidl::ObjectView< ::fidl::StringView>> elem)The top-level namespace associated with the data:
* Is intended to group related data together and reduce data key collisions across
namespaces.
* May be shared by multiple clients, e.g., there could be multiple clients within the same
component or across components that want to expose related data and they would all use
the same namespace.
* Will be prefixed to every data key passed within that namespace in all feedback reports,
e.g., the annotation "version" would appear as "foo.version" in all feedback reports if
the namespace is "foo".
* Must match [a-z
\
-]+, i.e. only lowercase letters and hyphens or this will result in a
ZX_ERR_INVALID_ARGS epitaph.
* Must not match a reserved namespace used internally for platform data, e.g., "build", or
this will result in a ZX_ERR_INVALID_ARGS epitaph. The list of reserved namespaces is
internal and subject to change for now.
bool has_annotations ()void clear_annotations ()Clears the annotations field.
This method should be used sparingly, such as only during tests, as it has
O(number_of_fields) complexity.
::fidl::VectorView< ::fuchsia_feedback::wire::Annotation> & annotations ()A vector of key-value string pairs, e.g., `
<
"version", "1.2.3.45">`.
Keys:
* Should be unique as only the latest value for a given key in the vector will be
considered.
* Must match [a-z
\
-
.
]+, i.e. only lowercase letters, hyphens and periods. Use periods for
sub-namespacing, e.g., "build.label" and "build.type", so that related annotations are
grouped together (here related to "build") when sorted lexicographically.
BuilderImpl & annotations (Wrapper_Ignore_Me_< ::fidl::ObjectView< ::fidl::VectorView< ::fuchsia_feedback::wire::Annotation>>> elem)A vector of key-value string pairs, e.g., `
<
"version", "1.2.3.45">`.
Keys:
* Should be unique as only the latest value for a given key in the vector will be
considered.
* Must match [a-z
\
-
.
]+, i.e. only lowercase letters, hyphens and periods. Use periods for
sub-namespacing, e.g., "build.label" and "build.type", so that related annotations are
grouped together (here related to "build") when sorted lexicographically.
Protected Methods
void WireTableBaseBuilder< ::fuchsia_feedback::wire::ComponentData, BuilderImpl> (::fidl::ObjectView< ::fidl::WireTableFrame< ::fuchsia_feedback::wire::ComponentData>> && frame)