Jérôme Steunou
Jérôme Steunou
Make sense. Thank you.
I understand the logic but I'm in favor of using `render` event for this case. I remember from 0.9 to 1.x then to 2.x I went from onShow then onDOM......
I understand but could seems like https://xkcd.com/927/ from Marionette user PoV.
About PR I would rather consider fixes for the current version of any kind (doc or src code) on `master` and new things of any kind on `next`
Something like that. We are using git flow at work, help a lot for cases like this one. One rule is that `master` is almighty and never directly changes. A...
So it will goes: - fixes of all kind (src & doc) `master` - new things of all kind into `next` - breaking changes as pending PR until ready for...
> Personally I think that the ideal fix would be for regions to never be initialized unless getRegion is called, so they wouldn't be in the constructor at all. @paulfalgout...
To second that, I'm not a big fan of accessing view from behavior. Maybe a little more abstraction on all the cases that today force us to do `this.view...` could...
To much work as a breaking change?
1. I also disapprove anonymous region. Never done and already thinks about edge cases that could break into user code. For some it could work, until... 2. named region is...