Implement setRenderer destructive option

[blikblum]

Proposed changes

• when passing an options hash to setRenderer with destructive: false, do not reinit regions on view re-render

Link to the issue: #3427

[coveralls]

Coverage remained the same at 100.0% when pulling a986fdd on blikblum:setrenderer-destructive into ba77bc0 on marionettejs:next.

[paulfalgout]

I'd support this for an experimental API. Looking forward to v4.x and v5 for region improvements and I don't want to box ourselves in.

[blikblum]

I'm ok with marking as an experimental API.
In fact, i think the renderer api should be extended to handle other things like dom:refresh and dom:remove events that does not make sense with non destructive renderers

[scott-w]

I'm a fan overall, I just think the naming could be improved (see my comment).

[scott-w]

I think the feature could be good, though I don't like the name.

Maybe just call this reInitializeRegion or maybe preserveRegion so the flag check can be options.preserveRegion.

[blikblum]

I'm fine changing the name but should not be region specific. This flag may be needed for other things than reinitialize region like for example adding an onReady event which would have a different behavior from destructive and non destructive regions.

[scott-w]

What about preventDestroy? It's used in stuff like region.show and it feels like it does a similar job.

[paulfalgout]

Something like this may make it to https://github.com/marionettejs/marionette