Yes, as JSON API follows HATEOAS quite strictly it should be possible to discover the API schema dynamically as the system traverses these relationships.This would be a nice approach.

What I was about to start experimenting with was more basic than that. I was intending to use the existing js-data schema definition but to try to add the ability to lazy load resources. This is because JSON API defines relationship links which are discovered as the API is traversed, but does not necessarily provide the data for those related resources (Optionally provided in included data section).
So after requesting a resource, we would also need to add uninitialised related objects to the data store along with the Url that they should be initialised from. These could be considered lazy objects which would need to be initialized from their resource Url from the backing store / adapter.

The Url and status of the object e.g. Loaded or not for lazy objects could possibly be stored in metadata? I am new to js-data so am not sure if this is possible ?

An modified Http Adapter could then inspect this metadata and load the lazy objects as required ?

Once we have the data and their resource Urls stored we should have all the information required to do updates and deletes (As for any REST Api).

I'm fairly new to this so hope this is not too far off?

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions