See for story. We’ll want to modify any server-side processing for these fields to match what’s in the spec.
wait, we do need it in ElementsRequest, NotebooksRequest and Commit (unless you mean CommitsRequest but that’s already taken out there). there’s no way for a user to post a commit directly and they’re not supposed to be in Element(Json) when posted
just to clarify, the server is taking comment and source from ElementsRequest and NotebooksRequest and setting them as the source and comment in Commit
Is there a general way of handling that, e.g. all additionalProperties (or those nested in a field), are applied to the resulting Commit? In other words, what happens to fields that are not source and comment when using ElementsRequest to create a Commit?
there’s no other fields allowed in Requests besides those specified (requests don’t have additional properties)
That sounds like special handling of source and comment in the case of ElementsRequest, NotebooksRequest, and Commit. For the scope of this issue, I think we should spec it as-implemented.