Assigning function directly to "renderer" should no longer be encouraged

[boghyon]

Specifying the renderer without apiVersion: 2 (e.g. renderer: <fn>) causes falling back to the legacy string-based rendering even with semantic rendering APIs, i.e. no DOM-patching can be performed.

And according to UI5/openui5#2822, there won't be any implicit setting of the flag either.

Topics that mention renderer: <fn> should be all updated; informing that renderer: <fn> should no longer be used and that apiVersion: 2 should be explicitly set. E.g.:

renderer: function(oRM, oControl) {/*...*/}

renderer: {
 apiVersion: 2,
 render: function(oRM, oControl) {
 // ...
 }
}

[Thodd]

Hi @boghyon,

sorry this issue got lost somehow.
I'm adapting some parts of the Renderer documentation right now, so I adapt it where I find this inconsistency.

Additionally I'll see that I make a backlog item or something for a broader cleanup.
I guess there are a couple of occurrences... I haven't grep'ed yet.

BR,
Thorsten

[flovogt]

Hello @boghyon ,
Thank you for sharing this finding. I've created an internal incident 2280031655. The status of the issue will be updated here in GitHub.

[Thodd]

Hi @boghyon & @flovogt,

I'll close this issue with a reference on #17.

Initially I thought I could just replace the usage of the "renderer" function, but that's to superficial.
The goal should be to have more general rework of the rendering topic. So I'll drop this bandaid for now
and have created an internal backlog item based on @boghyon initial proposal in issue 17.
That should also cover the removal of renderer function usage in favor of an in-place object syntax.

PS: Backlog item id is CPOUI5FRAMEWORK-343 ;)

BR,
Thorsten