Demo Kit: Global Search Misses to Crawl Some References
See original GitHub issueTested OpenUI5 version:
- 1.56.4
- 1.59.0-SNAPSHOT
URL (minimal example if possible):
https://openui5nightly.hana.ondemand.com/#/search/QuickViewGroupElementType
Steps to reproduce the problem:
- Open the above page which shows the search results for e.g. QuickViewGroupElementType
- Go to this API reference page. Notice that QuickViewGroupElementType is clearly mentioned there.
What is the expected result?
The search result page includes all mentions of the searched query. In the above case, the API reference page of sap.m.QuickViewGroupElement
should be included in the result page as well.
What happens instead?
The result page doesn’t show everything even though the search query is clearly mentioned in other locations within Demo Kit.
Any other information? (attach screenshot if possible)
It would be nice if the global search is enhanced / fixed so that users can easily find out where the entered (enum) type is used. Currently, this doesn’t work.
For example, how can I find easily all uses of a certain type like sap.m.Button
?
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
How Search Engines Work: Crawling, Indexing, and Ranking
This chapter shows you how their robots crawl the Internet to find your site ... that some of your important pages are missing...
Read more >Build and Submit a Sitemap | Google Search Central
General sitemap guidelines. Use consistent, fully-qualified URLs. Google will crawl your URLs exactly as listed. For instance, if your site is ...
Read more >API Reference | Elastic App Search Documentation [8.5]
Enterprise Search API references provide curl examples for many API operations. ... Some API references use shell variables— define those variables in your ......
Read more >Global search stopped working | Thunderbird Support Forum
For the past two months, search hasn't been working. Even for emails that I know are there, search will give blank results or...
Read more >8 Manage Search in Oracle Fusion Applications
Select the application engine instance that contains the searchable objects to be managed to open the Enterprise Crawl and Search Framework Configuration ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
“A dot is a dot is a dot” (based loosely on this one)
My guess was wrong, it’s not a cleanup issue. When you search for “sap.m.InstanceManager.closeAllDialogs”, you’ll find the expected hit in MessageBox. The indexing currently doesn’t understand what it is indexing. Qualified names look all the same for it, it is not able to split “sap.m.InstanceManager.closeAllDialogs” into class name and method name.
I think we can improve this. At least in the context of a @link tag, we should be able to recognize cross references and handle them accordingly.
No, definitely not. If you search for the word “tapping” which is used in the same description as
InstanceManager
you’ll also find the MessageBox among the search hits.I guess the reason why
InstanceManager
is not found might be a too aggressive cleanup of the input text. Maybe all tags together with their content are removed (…InstanceManager…
), but that’s just a guess. I’ll look into it and let you know.