Change Details

Jade is setting an instance of a class to ParserOutput `$.JsConfigVars.entityTitle`

Jade is setting an instance of Title class to ParserOutput::setJSConfigVars which is then fails to serialize under`$.JsConfigVars.entityTitle` json-path. I do not understand how it worked before - JS config vars as I understand are serialized to JSON by OutputPage in order to deliver them to JS. This property is widely used in Jade frontend, but JSON-serialization of it would've failed before. Is there some special handling for Title class in the JS config?

Jade is setting an instance of aTitle class to ParserOutput `$t::setJSConfigVars which is then fails to serialize under`$.JsConfigVars.entityTitle` json-path. I do not understand how it worked before - JS config vars as I understand are serialized to JSON by OutputPage in order to deliver them to JS. This property is widely used in Jade frontend, but JSON-serialization of it would've failed before. Is there some special handling for Title class in the JS config?