@parca/client - npm Package Compare versions

Comparing version 0.16.122 to 0.16.123

CHANGELOG.md

@@ -6,2 +6,6 @@ # Change Log
 
+## 0.16.123 (2024-07-29)
+
+**Note:** Version bump only for package @parca/client
+
 ## 0.16.122 (2024-07-09)
@@ -8,0 +12,0 @@

dist/google/api/http.d.ts

@@ -36,3 +36,3 @@ import type { BinaryWriteOptions } from "@protobuf-ts/runtime";
 /**
- * # gRPC Transcoding
+ * gRPC Transcoding
  *
@@ -78,5 +78,4 @@ * gRPC Transcoding is a feature for mapping between a gRPC method and one or
  *
- * HTTP | gRPC
- * -----|-----
- * `GET /v1/messages/123456`  | `GetMessage(name: "messages/123456")`
+ * - HTTP: `GET /v1/messages/123456`
+ * - gRPC: `GetMessage(name: "messages/123456")`
  *
@@ -105,7 +104,5 @@ * Any fields in the request message which are not bound by the path template
  *
- * HTTP | gRPC
- * -----|-----
- * `GET /v1/messages/123456?revision=2&sub.subfield=foo` |
- * `GetMessage(message_id: "123456" revision: 2 sub: SubMessage(subfield:
- * "foo"))`
+ * - HTTP: `GET /v1/messages/123456?revision=2&sub.subfield=foo`
+ * - gRPC: `GetMessage(message_id: "123456" revision: 2 sub:
+ * SubMessage(subfield: "foo"))`
  *
@@ -140,6 +137,4 @@ * Note that fields which are mapped to URL query parameters must have a
  *
- * HTTP | gRPC
- * -----|-----
- * `PATCH /v1/messages/123456 { "text": "Hi!" }` | `UpdateMessage(message_id:
- * "123456" message { text: "Hi!" })`
+ * - HTTP: `PATCH /v1/messages/123456 { "text": "Hi!" }`
+ * - gRPC: `UpdateMessage(message_id: "123456" message { text: "Hi!" })`
  *
@@ -167,6 +162,4 @@ * The special name `*` can be used in the body mapping to define that
  *
- * HTTP | gRPC
- * -----|-----
- * `PATCH /v1/messages/123456 { "text": "Hi!" }` | `UpdateMessage(message_id:
- * "123456" text: "Hi!")`
+ * - HTTP: `PATCH /v1/messages/123456 { "text": "Hi!" }`
+ * - gRPC: `UpdateMessage(message_id: "123456" text: "Hi!")`
  *
@@ -199,10 +192,10 @@ * Note that when using `*` in the body mapping, it is not possible to
  *
- * HTTP | gRPC
- * -----|-----
- * `GET /v1/messages/123456` | `GetMessage(message_id: "123456")`
- * `GET /v1/users/me/messages/123456` | `GetMessage(user_id: "me" message_id:
- * "123456")`
+ * - HTTP: `GET /v1/messages/123456`
+ * - gRPC: `GetMessage(message_id: "123456")`
  *
- * ## Rules for HTTP mapping
+ * - HTTP: `GET /v1/users/me/messages/123456`
+ * - gRPC: `GetMessage(user_id: "me" message_id: "123456")`
  *
+ * Rules for HTTP mapping
+ *
  * 1. Leaf request fields (recursive expansion nested messages in the request
@@ -225,3 +218,3 @@ *    message) are classified into three categories:
  *
- * ### Path template syntax
+ * Path template syntax
  *
@@ -265,3 +258,3 @@ *     Template = "/" Segments [ Verb ] ;
  *
- * ## Using gRPC API Service Configuration
+ * Using gRPC API Service Configuration
  *
@@ -281,11 +274,10 @@ * gRPC API Service Configuration (service config) is a configuration language
  *
- * Example:
+ * The following example selects a gRPC method and applies an `HttpRule` to it:
  *
  *     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
+ * Special notes
  *
@@ -292,0 +284,0 @@ * When gRPC Transcoding is used to map a gRPC to JSON REST endpoints, the

package.json

 {
   "name": "@parca/client",
-  "version": "0.16.122",
+  "version": "0.16.123",
   "description": "Parca API Client",
@@ -28,3 +28,3 @@ "main": "dist/index.js",
   },
-  "gitHead": "c8ebc13e7bf1f28e6ea1bd43d719bab85c6a28b1"
+  "gitHead": "42342c1a093040c94a83beb1161beedcaa2f8580"
 }

src/google/api/http.ts

@@ -57,3 +57,3 @@ // @generated by protobuf-ts 2.9.4 with parameter generate_dependencies
 /**
- * # gRPC Transcoding
+ * gRPC Transcoding
  *
@@ -99,5 +99,4 @@ * gRPC Transcoding is a feature for mapping between a gRPC method and one or
  *
- * HTTP | gRPC
- * -----|-----
- * `GET /v1/messages/123456`  | `GetMessage(name: "messages/123456")`
+ * - HTTP: `GET /v1/messages/123456`
+ * - gRPC: `GetMessage(name: "messages/123456")`
  *
@@ -126,7 +125,5 @@ * Any fields in the request message which are not bound by the path template
  *
- * HTTP | gRPC
- * -----|-----
- * `GET /v1/messages/123456?revision=2&sub.subfield=foo` |
- * `GetMessage(message_id: "123456" revision: 2 sub: SubMessage(subfield:
- * "foo"))`
+ * - HTTP: `GET /v1/messages/123456?revision=2&sub.subfield=foo`
+ * - gRPC: `GetMessage(message_id: "123456" revision: 2 sub:
+ * SubMessage(subfield: "foo"))`
  *
@@ -161,6 +158,4 @@ * Note that fields which are mapped to URL query parameters must have a
  *
- * HTTP | gRPC
- * -----|-----
- * `PATCH /v1/messages/123456 { "text": "Hi!" }` | `UpdateMessage(message_id:
- * "123456" message { text: "Hi!" })`
+ * - HTTP: `PATCH /v1/messages/123456 { "text": "Hi!" }`
+ * - gRPC: `UpdateMessage(message_id: "123456" message { text: "Hi!" })`
  *
@@ -188,6 +183,4 @@ * The special name `*` can be used in the body mapping to define that
  *
- * HTTP | gRPC
- * -----|-----
- * `PATCH /v1/messages/123456 { "text": "Hi!" }` | `UpdateMessage(message_id:
- * "123456" text: "Hi!")`
+ * - HTTP: `PATCH /v1/messages/123456 { "text": "Hi!" }`
+ * - gRPC: `UpdateMessage(message_id: "123456" text: "Hi!")`
  *
@@ -220,10 +213,10 @@ * Note that when using `*` in the body mapping, it is not possible to
  *
- * HTTP | gRPC
- * -----|-----
- * `GET /v1/messages/123456` | `GetMessage(message_id: "123456")`
- * `GET /v1/users/me/messages/123456` | `GetMessage(user_id: "me" message_id:
- * "123456")`
+ * - HTTP: `GET /v1/messages/123456`
+ * - gRPC: `GetMessage(message_id: "123456")`
  *
- * ## Rules for HTTP mapping
+ * - HTTP: `GET /v1/users/me/messages/123456`
+ * - gRPC: `GetMessage(user_id: "me" message_id: "123456")`
  *
+ * Rules for HTTP mapping
+ *
  * 1. Leaf request fields (recursive expansion nested messages in the request
@@ -246,3 +239,3 @@ *    message) are classified into three categories:
  *
- * ### Path template syntax
+ * Path template syntax
  *
@@ -286,3 +279,3 @@ *     Template = "/" Segments [ Verb ] ;
  *
- * ## Using gRPC API Service Configuration
+ * Using gRPC API Service Configuration
  *
@@ -302,11 +295,10 @@ * gRPC API Service Configuration (service config) is a configuration language
  *
- * Example:
+ * The following example selects a gRPC method and applies an `HttpRule` to it:
  *
  *     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
+ * Special notes
  *
@@ -313,0 +305,0 @@ * When gRPC Transcoding is used to map a gRPC to JSON REST endpoints, the

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Worsened metrics

Total package byte prevSize

2171583

Lines of code

43716

decreased by-0.04%

No dependency changes