protobuf

Protocol Buffers - Google's data interchange format (grpc依赖) https://developers.google.com/protocol-buffers/

Tag: Branch: Tree: 6afb130dca

Éamonn McManus 39a1c6a46e In the Kotlin DSL, reference builder methods with property syntax. Instead of _builder.getFoo() and _builder.setFoo(value), the generated code now uses _builder.foo and _builder.foo = value. When compiling against the Java Proto API, this makes no difference, since the Kotlin compiler treats Java methods getFoo/setFoo as defining a Kotlin property foo. But if a compatible proto API is implemented in Kotlin then there is no such equivalence. Such an implementation would have to define either both forms or just the one that the DSL uses. For a Kotlin API it is more natural to use properties. Similarly, the generated Java methods getFoosList(), getFoosCount(), getFoosMap(), and getEnumValue() are accessed via property names (foosList, foosCount, foosMap, enumValue). (This is the second application of this change. The first had to be rolled back because it didn't handle conflict-resolution names correctly.) PiperOrigin-RevId: 629807104	7 months ago
..
main/kotlin/com/google/protobuf	Breaking Change: The base class for generated messages will be	11 months ago
test	In the Kotlin DSL, reference builder methods with property syntax.	7 months ago

Éamonn McManus 39a1c6a46e In the Kotlin DSL, reference builder methods with property syntax.

Instead of _builder.getFoo() and _builder.setFoo(value), the generated code now uses _builder.foo and _builder.foo = value. When compiling against the Java Proto API, this makes no difference, since the Kotlin compiler treats Java methods getFoo/setFoo as defining a Kotlin property foo. But if a compatible proto API is implemented in Kotlin then there is no such equivalence. Such an implementation would have to define either both forms or just the one that the DSL uses. For a Kotlin API it is more natural to use properties.

Similarly, the generated Java methods getFoosList(), getFoosCount(), getFoosMap(), and getEnumValue() are accessed via property names (foosList, foosCount, foosMap, enumValue).

(This is the second application of this change. The first had to be rolled back because it didn't handle conflict-resolution names correctly.)

PiperOrigin-RevId: 629807104

7 months ago

main/kotlin/com/google/protobuf

Breaking Change: The base class for generated messages will be

11 months ago

test

In the Kotlin DSL, reference builder methods with property syntax.

7 months ago