Community
Participate
Working Groups
Currently PersonProposalProvider only uses the identifier part in the content proposal. That means that if my id is "tehrnhoefer" but my pretty name "Thomas E", typing "thomas" wont include me in the list. I would assume most users would expect it to show up though. Also, repositories not having a user readable ID (e.g. an integer) will currently have a pretty useless "type & filter" functionality
Created attachment 199078 [details] patch v1 A first go on this. Will need to verify it fixes the behaviour in my connector, but it should. It will simply apply the filter text to the proposals a connector can provide (ID/prettyname pairs), and add the ID to the set if a match is found. A bit ugly due to the read-only set that .subset is returning, but I think creating a new TreeSet should not interfere anywhere.
Created attachment 199079 [details] mylyn/context/zip
I just verified that this works for my connector (and should do so for every connector supplying an ID/prettyName pair).
Thank for the great patch, Thomas! I have applied it to master and also made this work for Bugzilla. Additionally, I tweaked the matching strategy slightly to be case insensitive and to match any word of the pretty name.
Created attachment 199981 [details] screenshot