-
Notifications
You must be signed in to change notification settings - Fork 799
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
Create Node.js library #538
Comments
for reference https://grpc.io/docs/tutorials/basic/node.html |
Here are the docs on how to statically generate a grpc client in node: |
Nice. This may be something I can do and manually test with our current setup. I can look at porting the client tests too. Unless there is any existing work done on this? |
Not that i'm aware of! |
I started work on this and have created a project structure and generated the js files from .proto. Hope to spend more time on it this weekend |
We are currently using the REST API which works well but it may simplify things for new users to have a library to use with Node.js. When deploying a new Agones version with an API change, a developer would only have to update their library version. Ideally this would be published as a node module as this is idiomatic for Node.js.
There has been some discussion before about creating a gRPC client in Node.js, or the library could make REST calls directly. The gRPC route should result in generated code so would be more maintainable.
The text was updated successfully, but these errors were encountered: