@maxim_mazurok/gapi.client.servicenetworking-v1beta 0.0.20250127 → 0.0.20250202
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/index.d.ts +6 -2
- package/package.json +1 -1
package/index.d.ts
CHANGED
|
@@ -9,7 +9,7 @@
|
|
|
9
9
|
// This file was generated by https://github.com/Maxim-Mazurok/google-api-typings-generator. Please do not edit it manually.
|
|
10
10
|
// In case of any problems please post issue to https://github.com/Maxim-Mazurok/google-api-typings-generator
|
|
11
11
|
// Generated from: https://servicenetworking.googleapis.com/$discovery/rest?version=v1beta
|
|
12
|
-
// Revision:
|
|
12
|
+
// Revision: 20250202
|
|
13
13
|
|
|
14
14
|
/// <reference types="gapi.client" />
|
|
15
15
|
|
|
@@ -366,6 +366,8 @@ declare namespace gapi.client {
|
|
|
366
366
|
protobufPythonicTypesEnabled?: boolean;
|
|
367
367
|
/** Enables generation of asynchronous REST clients if `rest` transport is enabled. By default, asynchronous REST clients will not be generated. This feature will be enabled by default 1 month after launching the feature in preview packages. */
|
|
368
368
|
restAsyncIoEnabled?: boolean;
|
|
369
|
+
/** Disables generation of an unversioned Python package for this client library. This means that the module names will need to be versioned in import statements. For example `import google.cloud.library_v2` instead of `import google.cloud.library`. */
|
|
370
|
+
unversionedPackageDisabled?: boolean;
|
|
369
371
|
}
|
|
370
372
|
interface Field {
|
|
371
373
|
/** The field cardinality. */
|
|
@@ -650,7 +652,7 @@ declare namespace gapi.client {
|
|
|
650
652
|
value?: {[P in string]: any};
|
|
651
653
|
}
|
|
652
654
|
interface Page {
|
|
653
|
-
/** The Markdown content of the page. You can use (== include {path} ==) to include content from a Markdown file. The content can be used to produce the documentation page such as HTML format page. */
|
|
655
|
+
/** The Markdown content of the page. You can use ```(== include {path} ==)``` to include content from a Markdown file. The content can be used to produce the documentation page such as HTML format page. */
|
|
654
656
|
content?: string;
|
|
655
657
|
/** The name of the page. It will be used as an identity of the page to generate URI of the page, text of the link to this page in navigation, etc. The full page name (start from the root page name to this page concatenated with `.`) can be used as reference to the page in your documentation. For example: pages: - name: Tutorial content: (== include tutorial.md ==) subpages: - name: Java content: (== include tutorial_java.md ==) You can reference `Java` page using Markdown reference link syntax: `Java`. */
|
|
656
658
|
name?: string;
|
|
@@ -770,6 +772,8 @@ declare namespace gapi.client {
|
|
|
770
772
|
rangeName?: string;
|
|
771
773
|
}
|
|
772
774
|
interface SelectiveGapicGeneration {
|
|
775
|
+
/** Setting this to true indicates to the client generators that methods that would be excluded from the generation should instead be generated in a way that indicates these methods should not be consumed by end users. How this is expressed is up to individual language implementations to decide. Some examples may be: added annotations, obfuscated identifiers, or other language idiomatic patterns. */
|
|
776
|
+
generateOmittedAsInternal?: boolean;
|
|
773
777
|
/** An allowlist of the fully qualified names of RPCs that should be included on public client surfaces. */
|
|
774
778
|
methods?: string[];
|
|
775
779
|
}
|