Results 40 issues of Paul Falgout

If you call `getRegion` during a `region` before `isRendered()` is `true` you'll get a callstack error. We should throw a better error in these situations

bug

### Description Currently the best place to assume a view is ready to do most things is `onRender` (with the exception of needing to know the view is in the...

enhancement

If we want to replace `trigger` with `triggerMethod` https://github.com/marionettejs/backbone.marionette/issues/2508 ... it will really need to support the same API. `this.trigger('foo bar')` will trigger both `foo` and `bar` `this.triggerMethod('foo bar')` will...

feat:events

DO NOT MERGE This PR serves as a migration guide for moving to https://github.com/marionettejs/marionette with the exception of Radio integration. But it should make relevent breaking changes more obvious

https://github.com/marionettejs/backbone.marionette/pull/1984 `allowMissingEl` is currently missing from the `v3` documentation. However I think we should deprecate it. Maybe for removal in `v5`? I don't like it much as a solution. I...

feat:region

Currently in v4 if a region is `destroyed` the view the region belongs to will not trigger the `remove:region` event. They are only triggered if `view.removeRegion(name)` is used. All that...

A collectionview renders on `addChildView` and a view renders with `getRegion` in both of these cases we should prevent the render if these items are occurring inside of a `before:render`...

It can iterate over the reset event's `previousModels` This prevents a `collection.reset` from removing customly added views. We should also indicate that child view was created from a collection model...

This event is analogous to the region's show event. What it describes is that children were attached to the collection view. Yes, if they weren't already rendered they were rendered,...