still not usable, needs further design #3
Description
the new schema builder interface makes a lot of sense compared to the old checkbox interface, but the organization of the menus doesn't make sense. furthermore, doesn't really work and isn't fluid.
instead of fixing the crashers with the current implementation of the JSON HTTP Client builder, i would like to put design energy into the UI and flow.
current implementation:
after running the "test"
there are a number of issues here. i think it's a little unclear and unnatural how to use this, and another UI issue is that the schema builder takes up a lot of room, there's a lot of vertical scrolling.
what i actually had in mind
i wanted some sort of way to tie together the concept of unit testing, and knowing up front some example inputs (related to #4) and using that to actually execute said request against external server, in essence combining the steps of playing with an external API (like you would using a tool like curl or postman) and turning it into executable code.
as a UI puzzle, it may be too difficult to figure all of these things out at once. possibly the "testing" part of it could be figured out as part of #4 and implemented at another time. maybe "schema builder" should just let you paste JSON into it instead of doing requests itself.
i'm not sure about any of these ideas, and i don't know where to go with this.