Defines the HTTP configuration for an API service. It contains a list of
[HttpRule][google.api.HttpRule], each specifying the mapping of an RPC method
to one or more HTTP REST API methods.
When set to true, URL path parameters will be fully URI-decoded except in
cases of single segment matches in reserved expansion, where "%2F" will be
left encoded.
The default behavior is to not decode RFC 6570 reserved characters in multi
segment matches.
A list of HTTP configuration rules that apply to individual API methods.
**NOTE:** All service configuration rules follow "last one wins" order.
sizeCacheprotoimpl.SizeCachestateprotoimpl.MessageStateunknownFieldsprotoimpl.UnknownFields
Deprecated: Use Http.ProtoReflect.Descriptor instead.
(*T) GetFullyDecodeReservedExpansion() bool(*T) GetRules() []*HttpRule(*T) ProtoMessage()(*T) ProtoReflect() protoreflect.Message(*T) Reset()(*T) String() string
*T : google.golang.org/protobuf/reflect/protoreflect.ProtoMessage
*T : google.golang.org/protobuf/runtime/protoiface.MessageV1
*T : fmt.Stringer
*T : google.golang.org/protobuf/internal/impl.messageV1
*T : context.stringer
*T : os/signal.stringer
*T : runtime.stringer
# gRPC Transcoding
gRPC Transcoding is a feature for mapping between a gRPC method and one or
more HTTP REST endpoints. It allows developers to build a single API service
that supports both gRPC APIs and REST APIs. Many systems, including [Google
APIs](https://github.com/googleapis/googleapis),
[Cloud Endpoints](https://cloud.google.com/endpoints), [gRPC
Gateway](https://github.com/grpc-ecosystem/grpc-gateway),
and [Envoy](https://github.com/envoyproxy/envoy) proxy support this feature
and use it for large scale production services.
`HttpRule` defines the schema of the gRPC/REST mapping. The mapping specifies
how different portions of the gRPC request message are mapped to the URL
path, URL query parameters, and HTTP request body. It also controls how the
gRPC response message is mapped to the HTTP response body. `HttpRule` is
typically specified as an `google.api.http` annotation on the gRPC method.
Each mapping specifies a URL path template and an HTTP method. The path
template may refer to one or more fields in the gRPC request message, as long
as each field is a non-repeated field with a primitive (non-message) type.
The path template controls how fields of the request message are mapped to
the URL path.
Example:
service Messaging {
rpc GetMessage(GetMessageRequest) returns (Message) {
option (google.api.http) = {
get: "/v1/{name=messages/*}"
};
}
}
message GetMessageRequest {
string name = 1; // Mapped to URL path.
}
message Message {
string text = 1; // The resource content.
}
This enables an HTTP REST to gRPC mapping as below:
HTTP | gRPC
-----|-----
`GET /v1/messages/123456` | `GetMessage(name: "messages/123456")`
Any fields in the request message which are not bound by the path template
automatically become HTTP query parameters if there is no HTTP request body.
For example:
service Messaging {
rpc GetMessage(GetMessageRequest) returns (Message) {
option (google.api.http) = {
get:"/v1/messages/{message_id}"
};
}
}
message GetMessageRequest {
message SubMessage {
string subfield = 1;
}
string message_id = 1; // Mapped to URL path.
int64 revision = 2; // Mapped to URL query parameter `revision`.
SubMessage sub = 3; // Mapped to URL query parameter `sub.subfield`.
}
This enables a HTTP JSON to RPC mapping as below:
HTTP | gRPC
-----|-----
`GET /v1/messages/123456?revision=2&sub.subfield=foo` |
`GetMessage(message_id: "123456" revision: 2 sub: SubMessage(subfield:
"foo"))`
Note that fields which are mapped to URL query parameters must have a
primitive type or a repeated primitive type or a non-repeated message type.
In the case of a repeated type, the parameter can be repeated in the URL
as `...?param=A¶m=B`. In the case of a message type, each field of the
message is mapped to a separate parameter, such as
`...?foo.a=A&foo.b=B&foo.c=C`.
For HTTP methods that allow a request body, the `body` field
specifies the mapping. Consider a REST update method on the
message resource collection:
service Messaging {
rpc UpdateMessage(UpdateMessageRequest) returns (Message) {
option (google.api.http) = {
patch: "/v1/messages/{message_id}"
body: "message"
};
}
}
message UpdateMessageRequest {
string message_id = 1; // mapped to the URL
Message message = 2; // mapped to the body
}
The following HTTP JSON to RPC mapping is enabled, where the
representation of the JSON in the request body is determined by
protos JSON encoding:
HTTP | gRPC
-----|-----
`PATCH /v1/messages/123456 { "text": "Hi!" }` | `UpdateMessage(message_id:
"123456" message { text: "Hi!" })`
The special name `*` can be used in the body mapping to define that
every field not bound by the path template should be mapped to the
request body. This enables the following alternative definition of
the update method:
service Messaging {
rpc UpdateMessage(Message) returns (Message) {
option (google.api.http) = {
patch: "/v1/messages/{message_id}"
body: "*"
};
}
}
message Message {
string message_id = 1;
string text = 2;
}
The following HTTP JSON to RPC mapping is enabled:
HTTP | gRPC
-----|-----
`PATCH /v1/messages/123456 { "text": "Hi!" }` | `UpdateMessage(message_id:
"123456" text: "Hi!")`
Note that when using `*` in the body mapping, it is not possible to
have HTTP parameters, as all fields not bound by the path end in
the body. This makes this option more rarely used in practice when
defining REST APIs. The common usage of `*` is in custom methods
which don't use the URL at all for transferring data.
It is possible to define multiple HTTP methods for one RPC by using
the `additional_bindings` option. Example:
service Messaging {
rpc GetMessage(GetMessageRequest) returns (Message) {
option (google.api.http) = {
get: "/v1/messages/{message_id}"
additional_bindings {
get: "/v1/users/{user_id}/messages/{message_id}"
}
};
}
}
message GetMessageRequest {
string message_id = 1;
string user_id = 2;
}
This enables the following two alternative HTTP JSON to RPC mappings:
HTTP | gRPC
-----|-----
`GET /v1/messages/123456` | `GetMessage(message_id: "123456")`
`GET /v1/users/me/messages/123456` | `GetMessage(user_id: "me" message_id:
"123456")`
## Rules for HTTP mapping
1. Leaf request fields (recursive expansion nested messages in the request
message) are classified into three categories:
- Fields referred by the path template. They are passed via the URL path.
- Fields referred by the [HttpRule.body][google.api.HttpRule.body]. They are passed via the HTTP
request body.
- All other fields are passed via the URL query parameters, and the
parameter name is the field path in the request message. A repeated
field can be represented as multiple query parameters under the same
name.
2. If [HttpRule.body][google.api.HttpRule.body] is "*", there is no URL query parameter, all fields
are passed via URL path and HTTP request body.
3. If [HttpRule.body][google.api.HttpRule.body] is omitted, there is no HTTP request body, all
fields are passed via URL path and URL query parameters.
### Path template syntax
Template = "/" Segments [ Verb ] ;
Segments = Segment { "/" Segment } ;
Segment = "*" | "**" | LITERAL | Variable ;
Variable = "{" FieldPath [ "=" Segments ] "}" ;
FieldPath = IDENT { "." IDENT } ;
Verb = ":" LITERAL ;
The syntax `*` matches a single URL path segment. The syntax `**` matches
zero or more URL path segments, which must be the last part of the URL path
except the `Verb`.
The syntax `Variable` matches part of the URL path as specified by its
template. A variable template must not contain other variables. If a variable
matches a single path segment, its template may be omitted, e.g. `{var}`
is equivalent to `{var=*}`.
The syntax `LITERAL` matches literal text in the URL path. If the `LITERAL`
contains any reserved character, such characters should be percent-encoded
before the matching.
If a variable contains exactly one path segment, such as `"{var}"` or
`"{var=*}"`, when such a variable is expanded into a URL path on the client
side, all characters except `[-_.~0-9a-zA-Z]` are percent-encoded. The
server side does the reverse decoding. Such variables show up in the
[Discovery
Document](https://developers.google.com/discovery/v1/reference/apis) as
`{var}`.
If a variable contains multiple path segments, such as `"{var=foo/*}"`
or `"{var=**}"`, when such a variable is expanded into a URL path on the
client side, all characters except `[-_.~/0-9a-zA-Z]` are percent-encoded.
The server side does the reverse decoding, except "%2F" and "%2f" are left
unchanged. Such variables show up in the
[Discovery
Document](https://developers.google.com/discovery/v1/reference/apis) as
`{+var}`.
## Using gRPC API Service Configuration
gRPC API Service Configuration (service config) is a configuration language
for configuring a gRPC service to become a user-facing product. The
service config is simply the YAML representation of the `google.api.Service`
proto message.
As an alternative to annotating your proto file, you can configure gRPC
transcoding in your service config YAML files. You do this by specifying a
`HttpRule` that maps the gRPC method to a REST endpoint, achieving the same
effect as the proto annotation. This can be particularly useful if you
have a proto that is reused in multiple services. Note that any transcoding
specified in the service config will override any matching transcoding
configuration in the proto.
Example:
http:
rules:
# Selects a gRPC method and applies HttpRule to it.
- selector: example.v1.Messaging.GetMessage
get: /v1/messages/{message_id}/{sub.subfield}
## Special notes
When gRPC Transcoding is used to map a gRPC to JSON REST endpoints, the
proto to JSON conversion must follow the [proto3
specification](https://developers.google.com/protocol-buffers/docs/proto3#json).
While the single segment variable follows the semantics of
[RFC 6570](https://tools.ietf.org/html/rfc6570) Section 3.2.2 Simple String
Expansion, the multi segment variable **does not** follow RFC 6570 Section
3.2.3 Reserved Expansion. The reason is that the Reserved Expansion
does not expand special characters like `?` and `#`, which would lead
to invalid URLs. As the result, gRPC Transcoding uses a custom encoding
for multi segment variables.
The path variables **must not** refer to any repeated or mapped field,
because client libraries are not capable of handling such variable expansion.
The path variables **must not** capture the leading "/" character. The reason
is that the most common use case "{var}" does not capture the leading "/"
character. For consistency, all path variables must share the same behavior.
Repeated message fields must not be mapped to URL query parameters, because
no client library can support such complicated mapping.
If an API needs to use a JSON array for request or response body, it can map
the request or response body to a repeated field. However, some gRPC
Transcoding implementations may not support this feature.
Additional HTTP bindings for the selector. Nested bindings must
not contain an `additional_bindings` field themselves (that is,
the nesting may only be one level deep).
The name of the request field whose value is mapped to the HTTP request
body, or `*` for mapping all request fields not captured by the path
pattern to the HTTP body, or omitted for not having any HTTP request body.
NOTE: the referred field must be present at the top-level of the request
message type.
Determines the URL pattern is matched by this rules. This pattern can be
used with any of the {get|put|post|delete|patch} methods. A custom method
can be defined using the 'custom' field.
Types that are assignable to Pattern:
*HttpRule_Get
*HttpRule_Put
*HttpRule_Post
*HttpRule_Delete
*HttpRule_Patch
*HttpRule_Custom
Optional. The name of the response field whose value is mapped to the HTTP
response body. When omitted, the entire response message will be used
as the HTTP response body.
NOTE: The referred field must be present at the top-level of the response
message type.
Selects a method to which this rule applies.
Refer to [selector][google.api.DocumentationRule.selector] for syntax details.
sizeCacheprotoimpl.SizeCachestateprotoimpl.MessageStateunknownFieldsprotoimpl.UnknownFields
Deprecated: Use HttpRule.ProtoReflect.Descriptor instead.
(*T) GetAdditionalBindings() []*HttpRule(*T) GetBody() string(*T) GetCustom() *CustomHttpPattern(*T) GetDelete() string(*T) GetGet() string(*T) GetPatch() string(*T) GetPattern() isHttpRule_Pattern(*T) GetPost() string(*T) GetPut() string(*T) GetResponseBody() string(*T) GetSelector() string(*T) ProtoMessage()(*T) ProtoReflect() protoreflect.Message(*T) Reset()(*T) String() string
*T : google.golang.org/protobuf/reflect/protoreflect.ProtoMessage
*T : google.golang.org/protobuf/runtime/protoiface.MessageV1
*T : fmt.Stringer
*T : google.golang.org/protobuf/internal/impl.messageV1
*T : context.stringer
*T : os/signal.stringer
*T : runtime.stringer
func (*Http).GetRules() []*HttpRule
func (*HttpRule).GetAdditionalBindings() []*HttpRule
The custom pattern is used for specifying an HTTP method that is not
included in the `pattern` field, such as HEAD, or "*" to leave the
HTTP method unspecified for this rule. The wild-card rule is useful
for services that provide content to Web (HTML) clients.
(*T) isHttpRule_Pattern()
*T : isHttpRule_Pattern
A simple descriptor of a resource type.
ResourceDescriptor annotates a resource message (either by means of a
protobuf annotation or use in the service config), and associates the
resource's schema, the resource type, and the pattern of the resource name.
Example:
message Topic {
// Indicates this message defines a resource schema.
// Declares the resource type in the format of {service}/{kind}.
// For Kubernetes resources, the format is {api group}/{kind}.
option (google.api.resource) = {
type: "pubsub.googleapis.com/Topic"
name_descriptor: {
pattern: "projects/{project}/topics/{topic}"
parent_type: "cloudresourcemanager.googleapis.com/Project"
parent_name_extractor: "projects/{project}"
}
};
}
The ResourceDescriptor Yaml config will look like:
resources:
- type: "pubsub.googleapis.com/Topic"
name_descriptor:
- pattern: "projects/{project}/topics/{topic}"
parent_type: "cloudresourcemanager.googleapis.com/Project"
parent_name_extractor: "projects/{project}"
Sometimes, resources have multiple patterns, typically because they can
live under multiple parents.
Example:
message LogEntry {
option (google.api.resource) = {
type: "logging.googleapis.com/LogEntry"
name_descriptor: {
pattern: "projects/{project}/logs/{log}"
parent_type: "cloudresourcemanager.googleapis.com/Project"
parent_name_extractor: "projects/{project}"
}
name_descriptor: {
pattern: "folders/{folder}/logs/{log}"
parent_type: "cloudresourcemanager.googleapis.com/Folder"
parent_name_extractor: "folders/{folder}"
}
name_descriptor: {
pattern: "organizations/{organization}/logs/{log}"
parent_type: "cloudresourcemanager.googleapis.com/Organization"
parent_name_extractor: "organizations/{organization}"
}
name_descriptor: {
pattern: "billingAccounts/{billing_account}/logs/{log}"
parent_type: "billing.googleapis.com/BillingAccount"
parent_name_extractor: "billingAccounts/{billing_account}"
}
};
}
The ResourceDescriptor Yaml config will look like:
resources:
- type: 'logging.googleapis.com/LogEntry'
name_descriptor:
- pattern: "projects/{project}/logs/{log}"
parent_type: "cloudresourcemanager.googleapis.com/Project"
parent_name_extractor: "projects/{project}"
- pattern: "folders/{folder}/logs/{log}"
parent_type: "cloudresourcemanager.googleapis.com/Folder"
parent_name_extractor: "folders/{folder}"
- pattern: "organizations/{organization}/logs/{log}"
parent_type: "cloudresourcemanager.googleapis.com/Organization"
parent_name_extractor: "organizations/{organization}"
- pattern: "billingAccounts/{billing_account}/logs/{log}"
parent_type: "billing.googleapis.com/BillingAccount"
parent_name_extractor: "billingAccounts/{billing_account}"
For flexible resources, the resource name doesn't contain parent names, but
the resource itself has parents for policy evaluation.
Example:
message Shelf {
option (google.api.resource) = {
type: "library.googleapis.com/Shelf"
name_descriptor: {
pattern: "shelves/{shelf}"
parent_type: "cloudresourcemanager.googleapis.com/Project"
}
name_descriptor: {
pattern: "shelves/{shelf}"
parent_type: "cloudresourcemanager.googleapis.com/Folder"
}
};
}
The ResourceDescriptor Yaml config will look like:
resources:
- type: 'library.googleapis.com/Shelf'
name_descriptor:
- pattern: "shelves/{shelf}"
parent_type: "cloudresourcemanager.googleapis.com/Project"
- pattern: "shelves/{shelf}"
parent_type: "cloudresourcemanager.googleapis.com/Folder"
Optional. The historical or future-looking state of the resource pattern.
Example:
// The InspectTemplate message originally only supported resource
// names with organization, and project was added later.
message InspectTemplate {
option (google.api.resource) = {
type: "dlp.googleapis.com/InspectTemplate"
pattern:
"organizations/{organization}/inspectTemplates/{inspect_template}"
pattern: "projects/{project}/inspectTemplates/{inspect_template}"
history: ORIGINALLY_SINGLE_PATTERN
};
}
Optional. The field on the resource that designates the resource name
field. If omitted, this is assumed to be "name".
Optional. The relative resource name pattern associated with this resource
type. The DNS prefix of the full resource name shouldn't be specified here.
The path pattern must follow the syntax, which aligns with HTTP binding
syntax:
Template = Segment { "/" Segment } ;
Segment = LITERAL | Variable ;
Variable = "{" LITERAL "}" ;
Examples:
- "projects/{project}/topics/{topic}"
- "projects/{project}/knowledgeBases/{knowledge_base}"
The components in braces correspond to the IDs for each resource in the
hierarchy. It is expected that, if multiple patterns are provided,
the same component name (e.g. "project") refers to IDs of the same
type of resource.
The plural name used in the resource name and permission names, such as
'projects' for the resource name of 'projects/{project}' and the permission
name of 'cloudresourcemanager.googleapis.com/projects.get'. It is the same
concept of the `plural` field in k8s CRD spec
https://kubernetes.io/docs/tasks/access-kubernetes-api/custom-resources/custom-resource-definitions/
Note: The plural form is required even for singleton resources. See
https://aip.dev/156
The same concept of the `singular` field in k8s CRD spec
https://kubernetes.io/docs/tasks/access-kubernetes-api/custom-resources/custom-resource-definitions/
Such as "project" for the `resourcemanager.googleapis.com/Project` type.
Style flag(s) for this resource.
These indicate that a resource is expected to conform to a given
style. See the specific style flags for additional information.
The resource type. It must be in the format of
{service_name}/{resource_type_kind}. The `resource_type_kind` must be
singular and must not include version numbers.
Example: `storage.googleapis.com/Bucket`
The value of the resource_type_kind must follow the regular expression
/[A-Za-z][a-zA-Z0-9]+/. It should start with an upper case character and
should use PascalCase (UpperCamelCase). The maximum number of
characters allowed for the `resource_type_kind` is 100.
sizeCacheprotoimpl.SizeCachestateprotoimpl.MessageStateunknownFieldsprotoimpl.UnknownFields
Deprecated: Use ResourceDescriptor.ProtoReflect.Descriptor instead.
(*T) GetHistory() ResourceDescriptor_History(*T) GetNameField() string(*T) GetPattern() []string(*T) GetPlural() string(*T) GetSingular() string(*T) GetStyle() []ResourceDescriptor_Style(*T) GetType() string(*T) ProtoMessage()(*T) ProtoReflect() protoreflect.Message(*T) Reset()(*T) String() string
*T : google.golang.org/protobuf/reflect/protoreflect.ProtoMessage
*T : google.golang.org/protobuf/runtime/protoiface.MessageV1
*T : fmt.Stringer
*T : google.golang.org/protobuf/internal/impl.messageV1
*T : context.stringer
*T : os/signal.stringer
*T : runtime.stringer
Defines a proto annotation that describes a string field that refers to
an API resource.
The resource type of a child collection that the annotated field
references. This is useful for annotating the `parent` field that
doesn't have a fixed resource type.
Example:
message ListLogEntriesRequest {
string parent = 1 [(google.api.resource_reference) = {
child_type: "logging.googleapis.com/LogEntry"
};
}
The resource type that the annotated field references.
Example:
message Subscription {
string topic = 2 [(google.api.resource_reference) = {
type: "pubsub.googleapis.com/Topic"
}];
}
Occasionally, a field may reference an arbitrary resource. In this case,
APIs use the special value * in their resource reference.
Example:
message GetIamPolicyRequest {
string resource = 2 [(google.api.resource_reference) = {
type: "*"
}];
}
sizeCacheprotoimpl.SizeCachestateprotoimpl.MessageStateunknownFieldsprotoimpl.UnknownFields
Deprecated: Use ResourceReference.ProtoReflect.Descriptor instead.
(*T) GetChildType() string(*T) GetType() string(*T) ProtoMessage()(*T) ProtoReflect() protoreflect.Message(*T) Reset()(*T) String() string
*T : google.golang.org/protobuf/reflect/protoreflect.ProtoMessage
*T : google.golang.org/protobuf/runtime/protoiface.MessageV1
*T : fmt.Stringer
*T : google.golang.org/protobuf/internal/impl.messageV1
*T : context.stringer
*T : os/signal.stringer
*T : runtime.stringer
Package-Level Variables (total 48, in which 19 are exported)
The hostname for this service.
This should be specified with no prefix or protocol.
Example:
service Foo {
option (google.api.default_host) = "foo.googleapi.com";
...
}
optional string default_host = 1049;
A designation of a specific field behavior (required, output only, etc.)
in protobuf messages.
Examples:
string name = 1 [(google.api.field_behavior) = REQUIRED];
State state = 1 [(google.api.field_behavior) = OUTPUT_ONLY];
google.protobuf.Duration ttl = 1
[(google.api.field_behavior) = INPUT_ONLY];
google.protobuf.Timestamp expire_time = 1
[(google.api.field_behavior) = OUTPUT_ONLY,
(google.api.field_behavior) = IMMUTABLE];
repeated google.api.FieldBehavior field_behavior = 1052;
See `HttpRule`.
optional google.api.HttpRule http = 72295728;
A definition of a client library method signature.
In client libraries, each proto RPC corresponds to one or more methods
which the end user is able to call, and calls the underlying RPC.
Normally, this method receives a single argument (a struct or instance
corresponding to the RPC request object). Defining this field will
add one or more overloads providing flattened or simpler method signatures
in some languages.
The fields on the method signature are provided as a comma-separated
string.
For example, the proto RPC and annotation:
rpc CreateSubscription(CreateSubscriptionRequest)
returns (Subscription) {
option (google.api.method_signature) = "name,topic";
}
Would add the following Java overload (in addition to the method accepting
the request object):
public final Subscription createSubscription(String name, String topic)
The following backwards-compatibility guidelines apply:
* Adding this annotation to an unannotated method is backwards
compatible.
* Adding this annotation to a method which already has existing
method signature annotations is backwards compatible if and only if
the new method signature annotation is last in the sequence.
* Modifying or removing an existing method signature annotation is
a breaking change.
* Re-ordering existing method signature annotations is a breaking
change.
repeated string method_signature = 1051;
OAuth scopes needed for the client.
Example:
service Foo {
option (google.api.oauth_scopes) = \
"https://www.googleapis.com/auth/cloud-platform";
...
}
If there is more than one scope, use a comma-separated string:
Example:
service Foo {
option (google.api.oauth_scopes) = \
"https://www.googleapis.com/auth/cloud-platform,"
"https://www.googleapis.com/auth/monitoring";
...
}
optional string oauth_scopes = 1050;
An annotation that describes a resource definition, see
[ResourceDescriptor][].
optional google.api.ResourceDescriptor resource = 1053;
An annotation that describes a resource definition without a corresponding
message; see [ResourceDescriptor][].
repeated google.api.ResourceDescriptor resource_definition = 1053;
An annotation that describes a resource reference, see
[ResourceReference][].
optional google.api.ResourceReference resource_reference = 1055;
Package-Level Constants (total 12, all are exported)
Conventional default for enums. Do not use this.
Denotes a field as immutable.
This indicates that the field may be set once in a request to create a
resource, but may not be changed thereafter.
Denotes a field as input only.
This indicates that the field is provided in requests, and the
corresponding field is not included in output.
Specifically denotes a field as optional.
While all fields in protocol buffers are optional, this may be specified
for emphasis if appropriate.
Denotes a field as output only.
This indicates that the field is provided in responses, but including the
field in a request does nothing (the server *must* ignore it and
*must not* throw an error as a result of the field's presence).
Denotes a field as required.
This indicates that the field **must** be provided as part of the request,
and failure to do so will cause an error (usually `INVALID_ARGUMENT`).
Denotes that a (repeated) field is an unordered list.
This indicates that the service may provide the elements of the list
in any arbitrary order, rather than the order the user originally
provided. Additionally, the list's order may or may not be stable.
This resource is intended to be "declarative-friendly".
Declarative-friendly resources must be more strictly consistent, and
setting this to true communicates to tools that this resource should
adhere to declarative-friendly expectations.
Note: This is used by the API linter (linter.aip.dev) to enable
additional checks.
The resource has one pattern, but the API owner expects to add more
later. (This is the inverse of ORIGINALLY_SINGLE_PATTERN, and prevents
that from being necessary once there are multiple patterns.)
The "unset" value.
The resource originally had one pattern and launched as such, and
additional patterns were added later.
The unspecified value. Do not use.
The pages are generated with Goldsv0.3.2. (GOOS=linux GOARCH=amd64)
Golds is a Go 101 project developed by Tapir Liu.
PR and bug reports are welcome and can be submitted to the issue list.
Please follow @Go100and1 (reachable from the left QR code) to get the latest news of Golds.
