Changes
This release includes a fix for a bug in the web UI, a small fix for users that build grpcui from source, and some new features.
Web UI
These changes impact usage of both the command-line tool and the Go packages.
- The UI now includes a new tab, alongside the "Request", "Raw Request", and "Response" tabs: a "History" tab. As RPCs are invoked, this will store the details of the request to browser local storage. The user can then review the history of RPCs from this tab and select one to re-run.
- A runtime error would occur when trying to add elements (via green "+" button) to a repeated or map field that is nested inside the value of another map field. This has been fixed.
Command-line tool
This release adds some additional command-line flags:
- A new
-default-headerflag allows you to define request metadata headers from the command-line. Since request metadata is defined in the web UI, via form, the values indicated on the command-line are populated as defaults. So when you load the web UI, the metadata table will be populated with those values instead of being empty. - A new
-debug-clientflag allows you to enable debug logging inside the web UI client. The log messages are logged to the browser's JavaScript console. At the moment, these are fairly sparse, and related to internal callbacks during handling of updates to the UI when the request form is modified. But additional more useful log messages may be added in the future.
Go package "github.com/fullstorydev/grpcui"
This release fixes a build issue related to the removal of a package from a recent version of the "golang.google.com/grpc" module. This impacted users that linked in this package to their own module or that attempted to build grpcui from source in their own module workspace where the newer version of the gRPC module was in use. The work-arounds were to either explicitly upgrade the version of "github.com/fullstorydev/grpcurl" (a dependency of grpcui) to v1.6.1 or newer or to downgrade the version of "golang.google.com/grpc" to v1.31.0. This has now been remedied so upgrading to v1.1.0 of grpcui no longer requires either of these work-arounds and should be compatible with any constraints in one's go.mod file.