@nebius/js-sdk - v0.2.54
    Preparing search index...

    Interface FeatureSet

    =================================================================== Features

    TODO Enums in C++ gencode (and potentially other languages) are not well scoped. This means that each of the feature enums below can clash with each other. The short names we've chosen maximize call-site readability, but leave us very open to this scenario. A future feature will be designed and implemented to handle this, hopefully before we ever hit a conflict here.

    interface FeatureSet {
        "[customJson]"?: () => unknown;
        "[unknownFieldsSymbol]"?: Uint8Array<ArrayBufferLike>;
        $type: "google.protobuf.FeatureSet";
        defaultSymbolVisibility?: FeatureSet_VisibilityFeature_DefaultSymbolVisibility;
        enforceNamingStyle?: FeatureSet_EnforceNamingStyle;
        enumType?: FeatureSet_EnumType;
        fieldPresence?: FeatureSet_FieldPresence;
        jsonFormat?: FeatureSet_JsonFormat;
        messageEncoding?: FeatureSet_MessageEncoding;
        repeatedFieldEncoding?: FeatureSet_RepeatedFieldEncoding;
        utf8Validation?: FeatureSet_Utf8Validation;
        [key: symbol]: Uint8Array<ArrayBufferLike> | (() => unknown) | undefined;
    }

    Indexable

    • [key: symbol]: Uint8Array<ArrayBufferLike> | (() => unknown) | undefined

      =================================================================== Features

      TODO Enums in C++ gencode (and potentially other languages) are not well scoped. This means that each of the feature enums below can clash with each other. The short names we've chosen maximize call-site readability, but leave us very open to this scenario. A future feature will be designed and implemented to handle this, hopefully before we ever hit a conflict here.

      • Uint8Array<ArrayBufferLike>
      • () => unknown
          • (): unknown

          • =================================================================== Features

            TODO Enums in C++ gencode (and potentially other languages) are not well scoped. This means that each of the feature enums below can clash with each other. The short names we've chosen maximize call-site readability, but leave us very open to this scenario. A future feature will be designed and implemented to handle this, hopefully before we ever hit a conflict here.

            Returns unknown

      • undefined
    Index
    [customJson]? [unknownFieldsSymbol]? $type defaultSymbolVisibility? enforceNamingStyle? enumType? fieldPresence? jsonFormat? messageEncoding? repeatedFieldEncoding? utf8Validation?
    "[customJson]"?: () => unknown

    Returns a safe value for JSON logs.

    Type Declaration

      • (): unknown

      • Returns a safe value for JSON logs.

        Returns unknown

    "[unknownFieldsSymbol]"?: Uint8Array<ArrayBufferLike>

    Preserves protobuf fields that this SDK version does not recognize.

    $type: "google.protobuf.FeatureSet"

    Contains the fully qualified protobuf type name.

    defaultSymbolVisibility?: FeatureSet_VisibilityFeature_DefaultSymbolVisibility

    Contains the default_symbol_visibility protobuf field.

    enforceNamingStyle?: FeatureSet_EnforceNamingStyle

    Contains the enforce_naming_style protobuf field.

    enumType?: FeatureSet_EnumType

    Contains the enum_type protobuf field.

    fieldPresence?: FeatureSet_FieldPresence

    Contains the field_presence protobuf field.

    jsonFormat?: FeatureSet_JsonFormat

    Contains the json_format protobuf field.

    messageEncoding?: FeatureSet_MessageEncoding

    Contains the message_encoding protobuf field.

    repeatedFieldEncoding?: FeatureSet_RepeatedFieldEncoding

    Contains the repeated_field_encoding protobuf field.

    utf8Validation?: FeatureSet_Utf8Validation

    Contains the utf8_validation protobuf field.

    Settings
    Member Visibility

    On This Page
    Properties