Change REST API action to use well-defined fields
Right now, the Windmill REST API action simply inserts some TypeScript code, that the user has to modify. I would suggest changing the user experience to include a Postman-like experience, where you can add headers, cookies, hostname, path, HTTP method, and other inputs as separate, well-defined fields.
This would make the UX easier to insert REST API actions, versus writing TypeScript code, which I don't personally know.
4 Replies
The reason we chose typescript and not a GUI is because you can then write logic inside the code and also parametrize it with parameters like a normal script
My intuition is that fetch is as complex an interface as a postman gui
and fetch is super well documented https://developer.mozilla.org/en-US/docs/Web/API/fetch
fetch() global function - Web APIs | MDN
The global fetch() method starts the process of fetching a
resource from the network, returning a promise which is fulfilled once the response is
available.
Yeah, JS just isn't my primary language
I understand that but just filling fetch with props is similar to filling postman with props