-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
package generated protobuf code #9
Comments
progress: rchain-community/rvote@c86ae14 |
You can do the same with two commands.
Why I'm not jumping on generating fixed versions is because I'm planing to build code generation directly from gRPC reflection which is now enabled in RNode. And also no additional tool will be necessary. But having some clever GitHub action to generate fixed version would be nice to have. |
Those 2 commands are pretty much what I did. Publishing the result in npm would save a few hours here and there for folks like me. Putting it in a CDN along with a few more bits so that rchain is available with one I haven't gone as far as putting the generated code in npm... or even as far as figuring out how to treat different directories as different packages in my project. I wonder what gRPC reflection is or what its impact would be. Here's hoping for time to study it... |
More info about gRPC reflection and what this means for RNode is on PR where reflection is enabled. Basically, server can give the same information as in proto files so client code can be generated. |
It would be really handy to be able to just
npm install rchain-probuf
and get the stuff generated files with thernode-grpc-js
tool.Package versions could correspond to rnode versions.
The text was updated successfully, but these errors were encountered: