Let's wait until it's more stable.

I played around with the tool a little bit. I think it has great potential. Do you have a list of features you are planning to add?

It seems that development has stopped on JSON:API Document Viewer. I'm wondering if we could maybe incorporate a visualization of the resources in a response in a similar way. I think a combination of a browser to navigate between resources together with a visualization of the resources would be very nice.

Maybe even a feature to create, update and delete resources could be added. An editor to create and modify a JSON:API document might be very helpful for teaching and testing as well.

Thanks for the feedback!

I don't have a clear plan for this project, but I have some ideas.

Add HTML representation for the JSON:API document fetched

Reference:

• Add HTML representation for the JSON:API document fetched masterT/jsonapi-browser#2

Maybe be able to see the JSON:API document as HTML similar to

• the Ruby gem administrate
• the Vue.js application Vandal UI

Ex: Representing a JSON:API document with a resource as primary data:

Ex: Representing a JSON:API document with resource collection as primary data:

Support setting custom HTTP headers

Set custom HTTP headers (such as Authorization).

Maybe even a feature to create, update and delete resources could be added. An editor to create and modify a JSON:API document might be very helpful for teaching and testing as well.

I think it could be nice to edit and PATCH a fetched document using an HTML form. I might be possible because the "shape" of the document is already known.

For creating resources I think that without a proper specification of the resource it's not going to be easy to implement, nor pleasant for the user. The only solution I see is a form with a textarea to capture the JSON to send. 😬

That being said I'm working on creating a specification for API implementing JSON:API. The goal is to have a machine-readable specification of an API (something similar to RAML, swagger/OAS, API blueprint). With such a specification I could be possible to implement a tool to perform all the JSON:API operations. 🙂 My specification is at a very early stage, but if you want to sneak peek I created a gist.

I also have the idea to create an electron application to "bypass" the CORS, this way it could work on any API. This way it would be possible to set cookies (cross domain).