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
Building on #91, body is the one field that feels a little too magical. It just works, which is great, but maybe not entirely obvious.
Putting this issue here to discuss separately.
One thought I had was that if we pursued #91, it'd justify this move more to me. In this case, the fields definition would contain every property in the document that is generated without a preceding underscore (generated/reserved).
While I like the magic, I also wouldn't mind being more explicit in my schema definition. We could remove the bodyType option and instead have something like this:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Building on #91,
body
is the one field that feels a little too magical. It just works, which is great, but maybe not entirely obvious.Putting this issue here to discuss separately.
One thought I had was that if we pursued #91, it'd justify this move more to me. In this case, the
fields
definition would contain every property in the document that is generated without a preceding underscore (generated/reserved).While I like the magic, I also wouldn't mind being more explicit in my schema definition. We could remove the
bodyType
option and instead have something like this:This is just a first pass. TBH I don't like the shape of the API suggested above. Just something to get us thinking about this.
The text was updated successfully, but these errors were encountered: