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
{{ message }}
This repository has been archived by the owner on Apr 6, 2021. It is now read-only.
FYI, I am now veering back to the view that this should be handled by the implementation in a manner similar to view models (see https://restfulobjects.codeplex.com/workitem/35 ) - and that as far as RO is concerned the complex/aggregated type is an addressable object.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
ver: 1.0.0
raised by: richardpawson
ref: http://restfulobjects.codeplex.com/workitem/35
"The current preferred approach for this is to in-line the complex type - equivalent to if it had been eagerly loaded - but with no self link.
However, this development is dependent upon the RO spec formally defining the structure for in-lined objects."
The text was updated successfully, but these errors were encountered: