gnostic

gnostic copied to clipboard

Does this look like a change you'd accept? I'd like to override the content-type annotation of a streaming API to `text/event-stream` for use with server-sent events. However, when I add...

sloretz

Handle path patterns like /v1/{name=user/messages/*}

1

Fixes #457 Before, a path pattern like ``` /api/v1/{name=workspace/settings/*} ``` would generate a path like ``` /api/v1/workspace/{workspace}/* ``` now it generates ``` /api/v1/workspace/settings/{setting} ```

asavageiv

protoc-gen-open generates a bad path for some starred paths

1

Given this service definitions: ``` service WorkspaceService { rpc GetWorkspaceSetting(GetWorkspaceSettingRequest) returns (WorkspaceSetting) { option (google.api.http) = {get: "/api/v1/{name=workspace/settings/*}"}; option (google.api.method_signature) = "name"; } message GetWorkspaceSettingRequest { // The resource name...

asavageiv

Hi! Thanks for the work so far! Are there ways to omit methods and fields during OpenAPI3 generation based on [`google.api.field_visibility`](https://github.com/googleapis/googleapis/blob/master/google/api/visibility.proto) or any plans to add support? Example: ```protobuf service...

goulashify

feat(enum): improve enum support and naming in OpenAPI

1

- Add support for nested enums and avoid naming conflicts - Generate enum values for all enum types, regardless of `enum_type` setting - Use enum field names instead of numeric...

aide-cloud