on http://webdsl.org/reposearch/search/WebDSL

typing in setRequested gives no results or completion suggestions, but setRequestedURLNoEventsOrValidation does occur in the searched documents

Submitted by Danny Groenewegen on 14 February 2013 at 18:14

The problem resides in the full text analyzer we use for the autocompletion index. It is configured to match identifiers and method calls/imports (ie, it will match multiple words if they are seperated by a dot or hyphen). It therefore added requestlogEntry.setRequestedURLNoEventsOrValidation as a token for autocompletion. Normally, tokens such as setRequestedURLNoEventsOrValidation are likely to appear on other places as well (like the method declaration), not being part of a method call/import statement and thus also being treated as a token.

However, now that I think about it, it might be a better choice to only allow the hyphen as valid glue between words for constructing auto completion tokens (such that stratego identifiers with hyphens are still suggested on autocompletion). Note that the analyzer we use for the actual searching does not assume anything about `valid glue characters’ and will tokenize both the words and symbols as a separate token.