Searching the doc within the site has gotten difficult

[gdennie]

There needs to be a list all angular services with some sort of definitive synopsis about each. A glossary of sorts would suffice.

Presently, there are terms and service labels being used in descriptions that don't themselves have any easily accessible definitive definition.

In particular, $eval; the existing search facility produces a list of over twenty entries, non bearing the $eval name nor portending to be definitive, at least to a novice.

[btford]

@petebacondarwin thoughts on this?

[petebacondarwin]

@gdennie - nice GitHub username! I am not sure that the search is any worse than it has ever been.

Right now, all documents in the system that contain the search term are displayed. I believe they are ordered by occurrence but with extra weight applied to the term appearing in the title. Since $eval is not a service but a method on the RootScope type, it is not so easy to give this a higher rating as it stands.

In the guide section of the search results, the top two items are "Expressions" and "Scopes" which will in fact give quite a lot of useful information about this.

But I agree that we should refactor our search to also give weight to method names in the API pages.

[gdennie]

It will be more useful to provide a list of occurrences along with with a portion of each context so that we can discern whether it satisfies. Merely listing titles of documents in which the phrase occurs is insufficient. For example:

phrase: > $eval____________________

results:___
1: Angular expression yourself, use the $eval() method. Example
2: blabh blah $eval blah blah
3: blah blah $eval
4: ... $eval ...

However, I just noticed that a search for $eval returns results whose text does not even contain the word, $eval. This refinement would now seem to make finding out what $eval does particularly difficult.