Shawn
Shawn
What about using Json.Net -- I believe it maintains comments as long as you use JObject
I love the ideas and it would be great to see this almost as a provider model concept with the ability to create and configure different providers for different destinations....
excellent -- one request, it would be nice to be able to configure what relationship attributes were included in the output :smile:
would that require that we use the GET functionality to specify the attributes? Or is it more of a way of indicating which attributes are used via the schema editor...
I am not sure I understand. How can I use the information about to create a new property on my entity that returns the attribute information for relationships via the...
Sounds good :smile: Question, any chance this attribute that contains the related attributes that is returned on the node query could be used to write updates to back via POST?...
Any thought on this? Right now, for every entity retrieved I need to make a corresponding HTTP GET request to retrieve the relationship attributes. On mobile and low bandwidth connections...
@amorgner I was thinking about this and I don't think the _structr_graph (or _graph) output is going to be very usable. It doesn't line up to any existing entity structure...
+1. It would also be great if new views were automatically added (with no access as the default)
@cmorgner -- thanks I have looked at using cypher queries they are not very friends for REST clients (mobile applications, 3rd party integrations) that they go around the schema that...