Community
Participate
Working Groups
Currently the index is only used to find the location of global functions but then those functions and the fiels they are in still have to be parsed, inferred, and bound. All the information to create a content assist suggestion should be stored in the index so that these functions do not need to be parsed, inferred, and bound every time content assist is invoked.
Created attachment 199703 [details] Fix Patch This patch primarily updates the MethodPattern to store all the information about a function that is needed to create a content assist proposal. The rest of the changes are to then either help get that information to the MehtodPattern, or leverage the new information now stored in the index. Have also added a bunch of new JUnits to test all of this.
Created attachment 199704 [details] Updated Testing Zip This is an updated testing zip for org.eclipse.wst.jsdt.ui.tests/testresources for the updated JUnits.
Created attachment 199712 [details] Fix Patch - Update 1 same as last patch except I have added more documentation. I have a bit more documentation to do.
Created attachment 199775 [details] Fix Patch - Update 2 Finished documenting. Also had to add code to BasicSearchEngine#searchAllFunctions to deal with working copies.
Created attachment 199862 [details] Fix Patch - Update 3 Same as last patch except I removed a piece of code I commented out.
I think we are good to go on this.
Created bug 352499 to put this in head as well. merged patch there.
Created attachment 199943 [details] Fix Patch - Update 4 Same as last patch except small fix in Methodpattern#matchesDecodedKey. One of the lines was comparing the return qualificaiton to the return simple name rather then to the return qualification of the pattern to try and match.
Backed out the patch that was checked in on 07/20 because it breaks search and the SelectionEngine for functions.
Needs a lot more study to avoid breaking other functions.
