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
Routes or complex models sometimes contain field.Object types that would be useful to load into a specific object type on the client side to attach methods or additional meaning to it.
For instance, the client might want to load each location in the following resource into a Location object:
To make this easy to do, there could be a typed object. It would contain a type hint that would help clients add object hooks for that particular type. If a client would not recognize an object, it could simply parse it as regular JSON. The type hints would be an additional property such as "$type": "location". Each type should have its own definition in the schema, but it wouldn't have any links attached to it.
The text was updated successfully, but these errors were encountered:
Routes or complex models sometimes contain
field.Object
types that would be useful to load into a specific object type on the client side to attach methods or additional meaning to it.For instance, the client might want to load each location in the following resource into a
Location
object:To make this easy to do, there could be a typed object. It would contain a type hint that would help clients add object hooks for that particular type. If a client would not recognize an object, it could simply parse it as regular JSON. The type hints would be an additional property such as
"$type": "location"
. Each type should have its own definition in the schema, but it wouldn't have any links attached to it.The text was updated successfully, but these errors were encountered: