Community
Participate
Working Groups
renamed query is dropped from the task working set
Steffen: did you make changes here? I had this working previously. Have not verified the failure.
Not that I know of. I haven't touched the working set code.
Steffen: could you please investigate? I can try to get to it later tonight if this isn't high enough on your stack.
Will take a look now.
I have committed a (failing) test. The query uses the description as the handle. If that changes it is dropped from the working set. Technically each edit of query removes and re-adds it to the task list so I am not sure how it would be possible to track a change of the description with the current API. Ideas?
Created attachment 85512 [details] mylyn/context/zip
If you edit a query while having working set active renaming works since the query is re-added to the working set right away. This will require API changes, deferring to 2.3.
Just to clarify, it will be re-added only to the active working set. If that query been used in some other inactive working sets, it is most probably going to be dropped from those.
Pushing off to 3.0 as this will require API changes.
Rob, reassigning to you since this is related to separating the handle from the query name.
Created attachment 99341 [details] work in progress
Created attachment 99342 [details] mylyn/context/zip
Created attachment 99401 [details] patch
Created attachment 99402 [details] mylyn/context/zip
Fixed for JIRA by separating handle and summary. Renaming queries will start working for other connectors when they are ported to the new task list model.