Open greenkeeper[bot] opened 6 years ago
dependency
backbone.marionette was updated from 3.5.1
to 4.1.0
.Update to this version instead 🚀
CollectionView#addChildView
now accepts a preventRender
option.el.ownerDocument.documentElement;
by default instead of document.documentElement
for querying, customizable via DomApi.getDocumentEl
.noConflict
for using multiple versions on the global scope.destroy
events.CollectionView
's emptyView
will now respect the childViewContainer
for attachment.Region._setElement
was added for internal use, but may be made public in a future release.The new version differs by 22 commits.
f3ebdb7
Bump and build v4
80f0018
Make Region.setElement private
30b10e6
Update dependencies and node version
0150684
Update test runners
0145444
Update unit tests
92c6a23
Update build to rollup
a22d2b5
Update eslint
9893405
Remove Cypress
e435908
Use ownerdocument for document element (#3655)
d48ecdc
Make CollectionView emptyView respect childViewContainer (#3653)
56aa35d
Introduce setElement to Region (#3641)
73be804
Preventing showing of shown view in a region (#3650)
343b6bc
Region calls empty if there is a currentView (#3649)
75bc0fe
_isDestroying guard for preventing multiple destroy call (#3636)
9347c19
Added addChildView preventRender logic (#3630)
There are 22 commits in total.
See the full diff
dependency
backbone.marionette was updated from 3.5.1
to 4.1.1
.dependency
backbone.marionette was updated from 3.5.1
to 4.1.2
.
Version 4.0.0 of backbone.marionette was just published.
The version 4.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of backbone.marionette.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
v4.0.0v4.0.0 view commit logs
Breaking Changes
The breaking changes are documented in the upgrade guide.
Features
CollectionView
can now render a template in the same fashion of the removedCompositeView
.View#triggers
now passes the originating DOM event object as the final argument of the triggered Mn event.bindRequests
andunbindRequests
API.package.json
onjsnext:main
Documentation
The documentation structure was overhauled to provide a flow to reading through the docs.
Commits
The new version differs by 118 commits.
ec2f456
Bump and build v4
845b625
Merge branch 'master' into next
a9bbeeb
More upgrade docs
1af02e1
Update upgrade guides
17e8ef5
Initial upgrade guide refactoring
0c9d390
Export default for backwards compatibility
c78e429
Specify peer dependency more correctly as <= 1.9.x.
0e2fe01
Allow for use of Underscore 1.9.x.
1965ba8
Add yarn.lock file to .npmignore
dc61ea3
Added live example for 'Adding Regions' doc
b5aa8ce
Revamp documentation for v4 changes
d1ae411
Pass the container to
attachHtml
5e1466e
Prevent sort/filter when adding with an index
d89d05c
Add filteredChildren container to CollectionView
84feaba
Rename BackboneViewMixin to Events
There are 118 commits in total.
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: