Under-designing - HTTP calls are just "living maps"
After making the push / pull map box feature, I wanted to add HTTP calls - they are a pretty important building block for a system like this. So I was thinking... sure, I could make some UI with HTTP call features like you would expect... or, just open up the "request" key to be user-filled, and then the response is just added to that same map?
Make sense? Maybe? Check it out. I love "low-UI UI".
Assembling lots of puzzle pieces here..
In last years Data Rabbit demo flows, I used an Owen Wilson Wow API to show live-coding and map pulling.
— Ryan Robitaille (@ryrobes) June 28, 2023
The 2023 RVBBIT version is a bit different... ;)
Wows aside, HTTP block as a primitive "data type" (essentially) is great. Saves time and can be automated so much easier. pic.twitter.com/hONVzEnD2W
Bonus: you can select "client" or "server" for the call to be performed from - you know, if CORS it being a little pesky...