You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are two main use cases that I can see for this feature:
A library author that uses pbandk might want not want to expose auto-generated code to the end-users. For this, the author wants all classes generated by pbandk to have internal visibility modifier.
A library author that uses pbandk and employs explicit API mode who wants to expose proto classes to the end-users. For this, the author wants all classes generated by pbandk to have public visibility modifier.
The text was updated successfully, but these errors were encountered:
…r to protoc-gen-pbandk
Added the ability to compile pbandk-generated code with Kotlin's
"explicit API" mode turned on. This requires all types/functions/etc. to
have their visibility (`public`/`internal`/`private`) explicitly
spcified and, if they're public, have their type explicitly specified.
Also added a `visibility` option for `protoc-gen-pbandk` to allow
changing the visibility of pbandk-generated code from the default
`public` visibility to `internal`.
Fixes#190.
…r to protoc-gen-pbandk
Added the ability to compile pbandk-generated code with Kotlin's
"explicit API" mode turned on. This requires all types/functions/etc. to
have their visibility (`public`/`internal`/`private`) explicitly
specified and, if they're public, have their type explicitly specified.
Also added a `visibility` option for `protoc-gen-pbandk` to allow
changing the visibility of pbandk-generated code from the default
`public` visibility to `internal`.
Fixes#190.
Discussed in #174
Originally posted by itegulov November 2, 2021
Motivation
There are two main use cases that I can see for this feature:
internal
visibility modifier.public
visibility modifier.The text was updated successfully, but these errors were encountered: