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
It is hard to track the @buf package versions. If not the IDE import substitutions, I would never learn the path from which I should import common things like Metadata, Address, BalancesResponse, etc.
It would be way easier to have only one entry point for such interfaces and @penumbra-zone/protobuf package is the great fit for it. We could improve two things at once:
Bundle the specific version of the @buf/... into a specific version of @penumbra-zone/protobuf. There won't be a need to separately install @buf packages by consumers and no more need to configure the @buf registry
Make the imports straightforward and only from one place
I don't have the exact solution on how to structure the protobuf package. One option is to put the interfaces next to the services it is used within. For example, Metadata is used in the ViewService, so it could be placed in @penumbra-zone/protobuf/view-service
The text was updated successfully, but these errors were encountered:
It is hard to track the
@buf
package versions. If not the IDE import substitutions, I would never learn the path from which I should import common things likeMetadata
,Address
,BalancesResponse
, etc.It would be way easier to have only one entry point for such interfaces and
@penumbra-zone/protobuf
package is the great fit for it. We could improve two things at once:@buf/...
into a specific version of@penumbra-zone/protobuf
. There won't be a need to separately install@buf
packages by consumers and no more need to configure the@buf
registryI don't have the exact solution on how to structure the
protobuf
package. One option is to put the interfaces next to the services it is used within. For example,Metadata
is used in theViewService
, so it could be placed in@penumbra-zone/protobuf/view-service
The text was updated successfully, but these errors were encountered: