I chased my tail for a good 2 hours today trying to figure out why I had parsing errors in my method's schema annotation. After a deeper dive than I'd ever like to do into Doctrine Annotations' internals, it turns out that you can use either a : or an = as a separator for key/value pairs.
I have a schema like:
* "store" = @JsonRpcParameterDefinition(
* schema = {"type" = "string", "enum" = {"google", "apple"}},
* required = true,
* ),
which includes an enum; I had been writing this as straight JSON-schema because the examples throughout the core module look like
* "permission" = @JsonRpcParameterDefinition(schema = {"type": "string"}),
(notice the colon instead of equal sign) which had my brain in JSON-mode. Turns out that Doctrine chokes on square brackets ([ and ]).
Set the schema annotation parameter to a JSON-schema string that includes square brackets and break your annotation.
Better documentation.
2.0
Code
Worse Than Failure. Approximates the unpleasant remark made by Drupal developers when they first encounter a particular (mis)feature.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This is a helpful comment and should be in the docs. RTBC.
Ultimately I think the better solution here would be to move from Doctrine annotations to attributes, but that's a different issue.