Submitting operations using the json1 syntax (directly or through helpers such as insertOp) fails the opContainsAnyField check, which checks the existence of a p field (which contains the path in json0).

Is it intended for sharedb-mongo to have built-in checks on the json0 syntax?
The call fails, but as mentioned in the comments, it is caught in sharedb and I don't see any side-effect apart from log pollution (for my usecase anyway).