Skip to content

Re-evaluate top-level Node interface #356

@murgatroid99

Description

@murgatroid99

The current top-level Node API exposes the set of things necessary to use the library, but not necessarily in the most reasonable way. Plus, load produces a possibly unintuitive combination of Protobuf.js output and grpc output.

It looks like there are two primary changes that need to be made for this:

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions