nscn.polaris2.protoc.bridge.codegen

Base class for a protoc code generator.

Implementors provide process and, if their .proto options are custom extensions, registerExtensions - without the registry the options arrive as unknown fields and silently read back as defaults.

The same object works as a standalone protoc-gen-* executable (via main) and as an in-JVM generator driven by the bridge (via run).

A CodeGeneratorRequest with its file protos already linked into FileDescriptors.

Linking matters for editions: FileDescriptor.buildFrom is what runs protobuf-java's feature resolution, so only after this do hasPresence, isPacked, isClosed and friends report edition-aware answers. Reading FileDescriptorProto directly would force every generator to reimplement that resolution.

Either the files a generator produced, or the reason it could not.

The descriptor queries a generator needs for editions, including stand-ins for the three protobuf-java methods that are package-private.

A generator should ask these questions through feature-resolved predicates - hasPresence, isPacked, isClosed - and not by testing the syntax. What is left here is the handful of cases where protobuf-java's public API has a gap.