You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, the GUI processes the Entrypoint and then for each hydra:Link endpoint available it uses the range property to know which node it's connected to. For non-collection Endpoints, this goes directly to the respective class. However, for the Collection endpoints, there are a couple of ways to do it. Right now the solution is to basically try to find the class which is related by extracting Collection from the Collection name and then showing the supported properties for this class. A more robust solution would be to get the range from the members' property in a collection, but this is not quite yet developed in the Spec. Another solution suggested by Vishal would be to get the expect property from the PUT operation in the Collection node. Either way, right now you can use all the classes operations and also use GET collection as default by simply not inputting properties in the form.
The text was updated successfully, but these errors were encountered:
Right now, the GUI processes the Entrypoint and then for each hydra:Link endpoint available it uses the range property to know which node it's connected to. For non-collection Endpoints, this goes directly to the respective class. However, for the Collection endpoints, there are a couple of ways to do it. Right now the solution is to basically try to find the class which is related by extracting Collection from the Collection name and then showing the supported properties for this class. A more robust solution would be to get the range from the members' property in a collection, but this is not quite yet developed in the Spec. Another solution suggested by Vishal would be to get the expect property from the PUT operation in the Collection node. Either way, right now you can use all the classes operations and also use GET collection as default by simply not inputting properties in the form.
The text was updated successfully, but these errors were encountered: