Since VRS backend could be either Parsoid or RESTBase, the error messages should reflect this. See T112330.
Description
Description
Details
Details
Subject | Repo | Branch | Lines +/- | |
---|---|---|---|---|
Clarify that both Parsoid and RESTBase can respond to VRS requests | mediawiki/extensions/Flow | master | +19 -16 |
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | • GWicke | T112330 In current VRS deployment scenarios, error logging should not assume Parsoid is the source of all errors. | |||
Resolved | • Catrope | T112566 Flow shouldn't assume Parsoid is source of all VRS errors |
Event Timeline
Comment Actions
Change 242929 had a related patch set uploaded (by Cscott):
Clarify that both Parsoid and RESTBase can respond to VRS requests
Comment Actions
@Catrope hopefully the patch answers your question. Flow doesn't have quite the same proliferation of "parsoiderror" types, but there are still some things that could be clarified.
Comment Actions
Change 242929 merged by jenkins-bot:
Clarify that both Parsoid and RESTBase can respond to VRS requests