Taffy

Taffy copied to clipboard

First, I really like the dashboard. I felt it gave me a great way to get started with a REST API. When I am trying to demonstrate the API via Taffy to some customers/clients, I get questions about how someone would use it. I've built a sample PowerShell script and I'm guessing it wouldn't take too much work to build a script using cURL. Would it be helpful to others to integrate these sample scripts into the dashboard? What does everyone else think?

I think using the dashboard as a "visual request builder" is an interesting idea, and it wouldn't take much to add a "show this request as a curl command" feature... The only potential down-side is that the dashboard UI is already growing a little cluttered, and #259 was created to address that concern. It's just something we'll need to keep in mind. If anyone has any UI suggestions, please feel free to chime in.

I guess before thinking about how to more efficiently use space it probably makes sense to determine how other people use the dashboard. I have disabled the dashboard in the production environment, and only use the dashboard for development. Do others keep the dashboard enabled in production?

If I were to enable the dashboard in a production environment, I would want to limit what fields showed up in the request builder. The goal would be to make the request building process as easy as possible without explicitly defining what security context the API uses (if any are implemented). Thoughts?

The general recommendation is definitely to disable the dashboard in production, so in that case the "visual request builder" concept won't be all that useful to your end-users if they don't have access to the dev/qa dashboard as well. They might, if the API is for internal use, so I think the feature still has a good amount of merit.

In the interest of getting Taffy 3.1 out sooner rather than later, I'm pushing this back to the next release.