Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 368185 - Change API function name for content assist
Summary: Change API function name for content assist
Status: RESOLVED FIXED
Alias: None
Product: Orion
Classification: ECD
Component: Client (show other bugs)
Version: 0.4   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 0.4 M2   Edit
Assignee: John Arthorne CLA
QA Contact:
URL:
Whiteboard:
Keywords: api
Depends on:
Blocks:
 
Reported: 2012-01-09 13:09 EST by John Arthorne CLA
Modified: 2012-01-10 16:52 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
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.