(no title)
notmedia | 3 years ago
> It doesn't remember your "environment". So if I call endpoint A and then click on endpoint B to try that, it forgets which environment is being targeted. Similarly, metadata is also specific to the request. If you use metadata for providing authorization headers, that means you have to enter the metadata separately every time you make a different request; there's no way to share metadata as an "environment".
Yeah, I have this in plans for taking environment and Metadata from previous tab - https://github.com/getezy/ezy/issues/30
> If you create a collection and click "Create", and it errors saying an imported proto resource wasn't found, the entire collection disappears.
Ha, interesting case, you selected the file and then just delete it before clicking create :) I will think how to handle this.
> The app uses the proto schema to show a list of endpoints, but it doesn't know anything about the message and response schemas, and you can't browse the types? It seems tedious to have to manually enter the request as a JSON payload.
This is the great point, was already mentioned earlier, I have plans to add auto-mocking feature for request payloads and autocompletion in code editor this will fix this issue. Also I will think for option to show raw Protobuf definitions
> Similarly, response is shown in JSON, rather than Proto data. So I can't see what the returned types actually are.
Maybe you have an idea on how we can represent decoded message (which an object) and map it to Protobuf Message definition?
> The "Request" and "Metadata" editors are super laggy to the point of being unusable. It takes several seconds for what I type to appear in the editor, and my computer's CPU usage goes to 150% while it's sitting there doing nothing. Is there some kind of autocompletion that's supposed to kick in that's going into overdrive?
Interesting, this is the first feedback about app performance. Can you open an issue and put more details there? I need to know app version, your OS, how much tabs opened and how much are you typing. Will be helpfull, but I try to reproduce it anyway.
> Clicking on an endpoint adds another tab. Click around and you end up with dozens of tabs. Seems a bit pointless.
Sorry, I can't reproduce this bug. You said clicking around, where exactly I need to click?
> No support for setting HTTP headers or seeing the returned headers.
You can set it in your Metadata and this should work as expected.
atombender|3 years ago
No, I had a proto file which imported another proto file, which could not be found, because I had not added its path to the import path list. Seems like it would be a common enough issue.
> Maybe you have an idea on how we can represent decoded message (which an object) and map it to Protobuf Message definition?
Something like Grip, maybe: https://gripgrpc.dev/.
> Interesting, this is the first feedback about app performance.
Appears to be related to the number of tabs. If I have only one tab open, it's not particularly laggy.
> Sorry, I can't reproduce this bug. You said clicking around, where exactly I need to click?
Click on an endpoint. It always opens a new tab.
notmedia|3 years ago
Ah, this make sense. I agree that this could be a common issue while importing a protobuf. I will fix this in next release :)
> Something like Grip, maybe: https://gripgrpc.dev/. Got it, we have a related discussion here -https://github.com/getezy/ezy/discussions/29 I will think how to show it, thank you!
> Appears to be related to the number of tabs. If I have only one tab open, it's not particularly laggy.
The main problem here is persistance (saving all data on the disk), and this make performance problems. I have plans to rewrite this section to improve it.
> Click on an endpoint. It always opens a new tab.
I think I need to create a poll :) Some users saying that they want to open new tab by one click, others wants double click.
And here I really don't know whats the better way of UX should be.