Skip to main content
Drupal API
User account menu
  • Log in

Breadcrumb

  1. Drupal Core 11.1.x
  2. EnumOptions.php

function EnumOptions::__construct

Constructor.

Parameters

array $data {: Optional. Data for populating the Message object.

@type bool $allow_alias Set this option to true to allow mapping different tag names to the same value. @type bool $deprecated Is this enum deprecated? Depending on the target platform, this can emit Deprecated annotations for the enum, or it will be completely ignored; in the very least, this is a formalization for deprecating enums. @type bool $deprecated_legacy_json_field_conflicts Enable the legacy handling of JSON field name conflicts. This lowercases and strips underscored from the fields before comparison in proto3 only. The new behavior takes `json_name` into account and applies to proto2 as well. TODO Remove this legacy behavior once downstream teams have had time to migrate. @type array<\Google\Protobuf\Internal\UninterpretedOption>|\Google\Protobuf\Internal\RepeatedField $uninterpreted_option The parser stores options it doesn't recognize here. See above. }

Overrides Message::__construct

File

vendor/google/protobuf/src/Google/Protobuf/Internal/EnumOptions.php, line 78

Class

EnumOptions
Generated from protobuf message <code>google.protobuf.EnumOptions</code>

Namespace

Google\Protobuf\Internal

Code

public function __construct($data = NULL) {
    \GPBMetadata\Google\Protobuf\Internal\Descriptor::initOnce();
    parent::__construct($data);
}
RSS feed
Powered by Drupal