Community
Participate
Working Groups
Current user is not set and highlighted in content assist if the address set is populated by the proposals provided by the connector.
Created attachment 198137 [details] always try to set currentUser when populating addressSet
I review this after I recreate the patch for bug# 168204 ([patch] support bugzilla's usermatchmode for matching names to email addresses).
Thanks for the patch Mike. I am not sure that we would want to make that change. The intention of the API is to provide control over the proposals to a client. Can you give an example of a concrete use case? Would you be able to explicitly add the repository user to the list of proposals?
Frank, I'll reassign this to the inbox for now until we have converged on the implementation.
Created attachment 198148 [details] set currentUser if it's in the proposals I see what you mean. The main purpose for me is to set the currentUser field to repository user so that the Tasktop Planner knows which to highlight as "me"; it's not necessary to add it the list as well. I just created another patch that will not alter the proposals but simply set currentUser if it's in the list. What do you think?
Mike, some changes were made to PersonProposalProvider recently which unfortunately broke your patch. Would you be able to attach a new version against the current master?
Created attachment 201360 [details] updated patch Sorry about the delay, Steffen. Here's the updated patch. This is also my first patch created with Git, so hopefully it will work for you.
Created attachment 201361 [details] mylyn/context/zip
Thanks Mike! I have applied the patch and made one minor adjustment. If a list of users is provided currentUser is set regardless. This avoids a few comparisons and should not do any harm.
Great! Thanks Steffen!
