Merge lp:~gary-wzl77/scope-aggregator/fix_1521528 into lp:scope-aggregator
Proposed by
Gary.Wang
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | Kyle Nitzsche | ||||
Approved revision: | 157 | ||||
Merged at revision: | 156 | ||||
Proposed branch: | lp:~gary-wzl77/scope-aggregator/fix_1521528 | ||||
Merge into: | lp:scope-aggregator | ||||
Diff against target: |
153 lines (+100/-2) 4 files modified
CMakeLists.txt (+1/-1) README.md (+33/-1) include/query.h (+1/-0) src/utils.cpp (+65/-0) |
||||
To merge this branch: | bzr merge lp:~gary-wzl77/scope-aggregator/fix_1521528 | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Kyle Nitzsche (community) | Approve | ||
Review via email: mp+279084@code.launchpad.net |
Commit message
Add display_order field to enable developer to set child scopes display order for keyword scope.
Merge branch that fixes bug lp:1521528 in scope-agg.
Description of the change
Add display_order field to enable developer to set child scopes display order for keyword scope.
To post a comment you must log in.
General Comment
This is an interesting feature. One of the advantages of keywords is that you do not know what scopes may be installed. Yet this feature allows you to set the order inside a keyword by scope ID. Clearly, this allows order control with keyword aggregation. Nice.
It raises the question: why not just declare them as "scope" json objects and thereby set the order absolutely. And the answer is: because keywords move the logic of what results to provide to the child scope and simplifies the aggregation. So I like it!