-
-
Notifications
You must be signed in to change notification settings - Fork 91
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Detangle object relationships, formalize path api
- This was done to clarify the scope and hierarchy of the affected objects. - The AppView instance is where the path setting should be done, even though it ultimately pokes into the methods by the same name within ResultCollection. - Code that previously used queryHelper.currentPath now delegate this through the methods provided by AppView. - Formalizing what needs to be implemented for custom ResultCollection models - it needs to provide getCurrentPath/setCurrentPath along with the relevant Backbone.Paginator.requestPager methods. This should be documented. - The instance of AppView.collection now keeps track of the path that the AppView should be on - no longer requiring fetching this value from queryHelper - A completely custom ResultCollection can be now provided. - Default ResultCollection implementation now constructs queryParser and queryHelper inside itself to keep as much of the Plone catalog and content type specific information out of the pattern itself to aid in allowing reuse without the unwanted Plone bits (specifically with the queryHelper stuff, it really had no place on the top level option object). - Default implementation of the queryParser and construction of queryHelper should remain unchanged except for its references to certain attributes that exist on the parent app objects (such as the AppView.toolbar).
- Loading branch information
1 parent
ff74dab
commit d35479f
Showing
7 changed files
with
72 additions
and
43 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters