Possibility to configure API return keys about rest-client-sdk HOT 4 CLOSED

The API we are using returns hydra:members instead of members. I think the two approach are possibles, and may vary depending on which output you choose. (or maybe it's a bug in my server implementation).

A quick (and a little dirty) solution may be to define in the configuration the key to access your collection members.

A quicker and dirtier solution is to test the members and the hydra:members key existance.

What do you think ?

from rest-client-sdk.

Well, I think it is my bad.
I just saw that the server of the api example I use, is over 2 years old.

http://www.markus-lanthaler.com/hydra/api-demo/issues/

I think the hydra:member key (and of course the hydra: prefix) is proposed somewhere between 2013 and today.

from rest-client-sdk.

I think the two way are valid ways :

If you look at the Json-ld playground, you can see inline examples of the context. It defines a kind of namespace.

The thing with your server is that the context override the members definition and refer directly to the hydra:members endpoint url.

from rest-client-sdk.

Fixed in 0.20.0, you now have a "collectionKey" in the mapping that allows you to specify a custom key

from rest-client-sdk.