| Summary: | Query hits with no task are not showing on Open/Activate Task dialogs | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Willian Mitsuda <wmitsuda> | ||||
| Component: | Mylyn | Assignee: | Mik Kersten <mik.kersten> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | Keywords: | helpwanted | ||||
| Version: | dev | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Willian Mitsuda
Fixed. Rob: note that this was one place where the change to not have query.getChildren() return hits caused this small regression. We're going to need to look at the design here and consider whether hits should be a kind of ITask even though they don't have local data. Created attachment 52371 [details]
mylar/context/zip
(In reply to comment #1) > We're going to > need to look at the design here and consider whether hits should be a kind of > ITask even though they don't have local data. > This is one thing that confused me the first time I looked at the source code, this distinction between a task and query hit, because they have a lot in common. There is something a little strange yet in this design, perhaps extract a superinterface of ITask and query hit. There is a lot of code in mylar that iterates over a collection of tasks and after that iterates over a collection of query hits. This way it can be simplified. Yes, well put and this refactoring is long overdue. Created bug 161734. |