Comments (1)
@alapativ2, FYI, versions prior to 1.2.0 actually used an HTML layout to display the response instead of the text area with the JSON contents. But it turns out that RPC schemas often have asymmetric message complexity: the request messages are often simple/small, but response message are often large/complex. So while it is usually reasonable to render a form with the request, rendering responses into HTML is often not reasonable (like for RPCs with large responses) and led to non-trivial performance issues.
There is actually a TODO in the code to provide an HTML layout for the response (in a way, restoring the old functionality), but it would likely be based on user-selection vs. being the default, so as to only be a possible performance issue when the user explicitly requests it to be rendered that way. BTW, things that were missing from the HTML response in those old pre-v1.2.0 versions (things which weren't added to the request HTML until v1.3.0) are extra response schema information. Ideally, if/when the HTML response feature is added, the structure would show not just the field names and values but also provide info about the field types and even have tool-tips/hover information to show fields' comments and options -- just like is available in the request form.
from grpcui.
Related Issues (20)
- -default-header would be clear when using -examples at the same time HOT 2
- Failed to dial target host "localhost:8181": context deadline exceeded HOT 3
- Can't I use Dockerfile? HOT 2
- where is the docker image hosted? HOT 5
- Import Error "lookup of '$ret6' failed HOT 3
- The browser displays a connection error. HOT 1
- How can I wait for stream answers? HOT 1
- Is gRPC curl still visible from `Raw request` tab?
- Runtime error: invalid memory address or nil pointer dereference HOT 4
- M1 grpcui -plaintext localhost:8023 Failed to compute set of methods to expose: proto: invalid syntax: "<unknown:0>" HOT 5
- Failed to compute set of methods to expose: EOF
- undefined: indent HOT 1
- Shareable grpcui link that auto-populates request
- Feature request: Searching RPC based on its name
- [Feature request] Allow re-compute headers on each grpc call HOT 2
- background image (grpc-bg.svg) is too large HOT 1
- run grpcui and got "Symbol not found: grpc.health.v1.Health" HOT 1
- Release v1 reflection changes as 1.4.2
- file content hadn't update after file upload, only after setting focus on text field
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from grpcui.