Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 368185

Summary: Change API function name for content assist
Product: [ECD] Orion Reporter: John Arthorne <john.arthorne>
Component: ClientAssignee: John Arthorne <john.arthorne>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 Keywords: api
Version: 0.4   
Target Milestone: 0.4 M2   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description John Arthorne CLA 2012-01-09 13:09:23 EST 
Currently a content assist service must implement a single function called "getKeywords". This is misleading, since it is not just for keywords but for all proposals. Also to me "get" implies a simple accessor function, but this will typically be long running computation. When I first started working on content assist I found this confusing, and I think we should tidy it up while we still can. I suggest we use a function called "computeProposals". We can easily check for a getKeywords function for backwards compatibility.