googleapis/go-genproto

The changefinder tool compares the current branch against a base reference (defaulting to origin/main) to identify which submodules have changed. It automatically excludes any submodules located within an internal directory. By default, it outputs a newline-delimited list of changed submodules to stdout.

go run ./internal/actions/cmd/changefinder

Before integrating this repository into your project, be aware of the following:

• Experimental Status: This repository is currently experimental. The package structure is subject to change.
• Source Verification: Because the structure may change, check the original source repositories for the specific protocol buffer's associated service to confirm its status.
• Well-known Types: Historically, the protobuf directory contained generated code for well-known types. These are now hosted in the google.golang.org/protobuf module. The packages in this repository use type aliases to forward declarations from the protobuf module to the google.golang.org/protobuf module.

You can install the generated Go packages for common protocol buffer types and gRPC code using the following command.

Warning: As of May 26, 2023, new submodules were introduced. You should upgrade your dependencies before 2024-03-01 to avoid ambiguous import errors with google.golang.org/genproto.

```bash
go get google.golang.org/genproto/...\n```

UniversalAction represents an action that is always available in the add-on toolbar menu, regardless of the current message context. Each action requires a user-visible Text description and one of two action types:

1. OpenLink: Opens a specific URL when the action is triggered.
2. RunFunction: Calls a specific endpoint (function) when the action is triggered.

Use the isUniversalAction_ActionType interface to implement these types.

// Example of a UniversalAction that runs a function
action := &gmail.UniversalAction{
    Text: "Add a new contact",
    ActionType: &gmail.UniversalAction_RunFunction{
        RunFunction: "myFunctionName",
    },
}

The SheetsAddOnManifest message type is used to configure specific triggers for a Google Sheets add-on. It allows you to override common homepage triggers and define specific behavior when file scope authorization is granted.

Key fields:

• HomepageTrigger: An optional *type.HomepageExtensionPoint that overrides the configuration from addOns.common.homepageTrigger.
• OnFileScopeGrantedTrigger: A *SheetsExtensionPoint that defines the endpoint to execute when file scope authorization is granted for a specific document/user pair.

import "google.golang.org/genproto/googleapis/apps/script/type/sheets"

manifest := &sheets.SheetsAddOnManifest{
    HomepageTrigger: homepageExtensionPoint, // type.HomepageExtensionPoint
    OnFileScopeGrantedTrigger: &sheets.SheetsExtensionPoint{
        RunFunction: "myOnScopeGrantedFunction",
    },
}

The google.apps.drive.labels.v2 package provides message types for defining fields within Google Drive labels. The core type is Field, which uses a oneof structure to support different data types for label fields, including text, integers, dates, selections, and user-defined options.

Key components of a Field include:

• Type-specific options: TextOptions, IntegerOptions, DateOptions, SelectionOptions, and UserOptions.
• Metadata: Properties, DisplayHints, SchemaCapabilities, and AppliedCapabilities.
• Lifecycle information: Lifecycle (tracking creators, updaters, and timestamps) and LockStatus.
• Selection specific types: SelectionOptions can contain a list of Choice objects, each with its own properties, display hints, and lifecycle metadata.

ByteStream is designed for reliable, large-scale data transfers. The core pattern for handling interruptions is:

1. Initiate Write: Start a Write stream with WriteOffset: 0.
2. Handle Failures: If the stream breaks, do not assume all sent data was saved.
3. Query Status: Call QueryWriteStatus(resource_name) to get the committed_size.
4. Resume: Start a new Write stream. Set the WriteOffset to the committed_size received in step 3. Begin sending data from that point forward.
5. Finalize: The write is not permanent until a WriteRequest is sent with finish_write: true and the server responds with a WriteResponse.

ContextualTrigger defines conditions that fire when an opened email meets specific criteria. When a trigger fires, it executes a specified OnTriggerFunction to create cards and update the UI.

Currently, the manifest supports:

• Unconditional Trigger: An UnconditionalTrigger that executes the OnTriggerFunction whenever any email message is opened.

// Example of an unconditional contextual trigger
trigger := &gmail.ContextualTrigger{
    OnTriggerFunction: "myOnTriggerFunction",
    Trigger: &gmail.ContextualTrigger_Unconditional{
        Unconditional: &gmail.UnconditionalTrigger{},
    },
}

The google.apps.drive.labels.v2beta package provides message types for defining fields within Google Drive labels. The core Field message uses a oneof pattern to support different data types, including text, integers, dates, selections, and user-defined options.

Key components of a Field include:

• Type-specific options: TextOptions, IntegerOptions, DateOptions, SelectionOptions, and UserOptions.
• Metadata and capabilities: Properties, DisplayHints, SchemaCapabilities, and AppliedCapabilities.
• Lifecycle information: Lifecycle (tracking creators, updaters, and timestamps) and LockStatus.
• Selection details: For selection-based fields, SelectionOptions contains a list of Choice objects, each with its own properties and display hints.