@daniel this seems to be related to MW rest API, is there a tag for that?

In T353859#9421445, @MSantos wrote:

@daniel this seems to be related to MW rest API, is there a tag for that?

I added the tag, though it's strily speaking not quite correct... VE doesn ot use the REST API. But then, it uses HtmlOutputParserHelper, which is defiend in the REST code, so I suppose the tag is still fair.

It seems this is the related code: https://codesearch.wmcloud.org/core/?q=rest-html-backend-error

If the "reason" is supposed to be shown to users, then it should be passed as a parameter to the localised error message (the MessageValue), rather than as a separate field that is neither human- nor machine-readable. It should then be propagated to VisualEditor errors as well.

@daniel my main doubt now is if this falls into the bucket "should be maintained by teams that own the endpoint" or if it's a "core" change that should be tagged to MediaWiki-Platform-Team, what's your opinion on that?

Logging code is on all servers now, but I'm not seeing anything in the HtmlOutputRendererHelper channel so far.

In T353859#9441418, @MSantos wrote:

@daniel my main doubt now is if this falls into the bucket "should be maintained by teams that own the endpoint" or if it's a "core" change that should be tagged to MediaWiki-Platform-Team, what's your opinion on that?

This ticket here is about how errors are propagated in VE and shown to the user. I think that's up to Editing.

Logging parsoid errors in HtmlOutputRendererHelper (T356157) is up to either Content Transform or MW Interface - that class is glue code between Parsoid and REST.