~bigbes/tarantool-protobuf: 06b2978a

codegen: resolve (tarantool.lua_package) via global type registry

The custom file option was being dropped silently: protoc encoded it
correctly into the FileDescriptorProto, but protobuf-go parked the
unknown extension in the message's unknown-fields tail because
E_LuaPackage was never registered with protoregistry.GlobalTypes. As a
result proto.GetExtension returned "" and every override the README
documented was a no-op — every caller fell through to the default
"<pkg>.<file>_pb" path resolution.

Register E_LuaPackage in init() and add a luatest regression that
asserts both the output path and the cross-file require strings honor
the option, parameterized over both codegen modes.

Eugene Blikh <bigbes@gmail.com> — 2026-05-17 03:36:06 UTC

Commit 06b2978a0f71c67829bbb516ecec6edf32f78667view raw patch

Parent(s): 76140b72

2 changed file(s)

FileStatus+
cmd/protoc-gen-tarantool/internal/gen/options.go M +11
test/codegen_lua_package_test.lua A +108