Plugin Feedback from an Alpha Developer

Hi team :wave: Reporting in from the trenches.

While my perspective is still fresh, I wanted to give back.

A few notes after successfully getting a plugin up and running

  • Easy win on the table: For the OpenAPI spec, you currently link to out to Swagger. How powerful would it be to suggest they ask GPT-4 for help? That’s exactly what I did and it worked beautifully.

  • When checking the localhost version it was a bit confusing when it would give the green light on the manifest and spec, and acknowledge it was triggering the use of the plugin, but then wouldn’t actually complete the request. Makes sense; you fetch from your backend and can’t hit my localhost, but I thought maybe you’d do it browser side for the localhost version. What’s my point? It’d be a huge help to make a quick note in the chat interface when it knows it’s a localhost plugin that it won’t be fetching the full response from your local server, and that it’s time to move it to a hosted endpoint to continue development.

  • Otherwise, my feedback is the fact that I have very little feedback. The docs and flow and the surprising simplicity of this whole system - it’s fantastic.

Thanks for the opportunity to work alongside you for something so historic.

Ken

1 Like

Fair, I did this as well, it did get it wrong a couple of times though.

It’d be a huge help to make a quick note in the chat interface when it knows it’s a localhost plugin that it won’t be fetching the full response from your local server, and that it’s time to move it to a hosted endpoint to continue development.

Not sure I understand this, can you elaborate?

1 Like