Get desktop application:
View/edit binary Protocol Buffers messages
Whether or not to treat an enum field as closed. This option is only applicable to enum fields, and will be removed in the future. It is consistent with the legacy behavior of using proto3 enum types for proto2 fields.
Used in:
Whether or not to generate the deprecated UnmarshalJSON method for enums. Can only be true for proto using the Open Struct api.
One of OPEN, HYBRID or OPAQUE.
Used in:
API_LEVEL_UNSPECIFIED results in selecting the OPEN API, but needs to be a separate value to distinguish between an explicitly set api level or a missing api level.
Used in:
Whether or not to treat an enum field as closed. This option is only applicable to enum fields, and will be removed in the future. It is consistent with the legacy behavior of using proto3 enum types for proto2 fields.
Allows creation of large Java enums, extending beyond the standard constant limits imposed by the Java language.
Whether to use the old default outer class name scheme, or the new feature which adds a "Proto" suffix to the outer class name. Users will not be able to set this option, because we removed it in the same edition that it was introduced. But we use it to determine which naming scheme to use for outer class name defaults.
Whether to nest the generated class in the generated file class. This is only applicable to *top-level* messages, enums, and services.
(message has no fields)
Used in:
Invalid default, which should never be used.
Do not nest the generated class in the file class.
Nest the generated class in the file class.
Fall back to the `java_multiple_files` option. Users won't be able to set this option.
The UTF8 validation strategy to use.
Used in:
Invalid default, which should never be used.
Respect the UTF8 validation behavior specified by the global utf8_validation feature.
Verifies UTF8 validity overriding the global utf8_validation feature. This represents the legacy java_string_check_utf8 option.