v0.2.1

This fixes an issue in the go.mod file that would prevent earlier versions from working with modules when using Go 1.13.

v0.2.0

Bugfix Release

This release addresses numerous issues that have been filed since the initial v0.1.0 release. The major version is still zero; we still want a little more activity and to tackle some other open issues before creating a 1.0 release.

• Added -unix command-line flag, for connecting to a server that is listening on a Unix domain socket.
• Added -max-time command-line flag, which applies default timeouts to RPCs issued via the UI.
• Added -max-msg-size command-line flag, which can override the default response message size limit of 4mb.
• Fixed a bug where entering a negative value for fields whose type is a signed 64-bit int would always fail validation, even if the value entered is in range.
• Fixed a bug where the grpcui's connection to an RPC server would never recover if the connection were broken (such as transient network issue or restarting the backend server). It now reconnects automatically, though may take some time to recover (subject to the Go gRPC client's auto-reconnect and exponential backoff policies).
• Fixed a bug that manifested in some responses not being correctly formatted as JSON. In particular, use of infinite or NaN double values in responses would cause error messages in the web UI.
• Fixed a bug where binary response metadata (headers or trailers) could cause error messages in the web UI or be rendered incorrectly.
• Fixed a bug where response messages that had values of type google.protobuf.Any could result in error messages in the web UI or be rendered incorrectly.

v0.1.0

Initial release

This first release has major version zero because the repo is not very mature yet. To our knowledge, the tool is feature-complete and fully functional. But the code base is young, and is lacking things like automated tests (so there are likely some bugs lurking, and maybe even a key missing feature or two).

We'd like to get more miles on the tool before we're ready to call it "1.0". Please file an issue if you find problems with the tool or have features you'd like to see added.