You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently Xplore does not return search results or provide any view when searching. Implementation of search can be exposed in the Xplore dashboard as well as the CLI as an added bonus.
Motivation
Currently Xplore is lacking the functionality.
Proposal
We can use a hosted solution and also expose this to the CLI. Elastic Search, Algolia, etc can be chosen.
The text was updated successfully, but these errors were encountered:
We definitely need a search functionality in xplore.
But that can only come once we have developed individual pages for transactions / blocks / addresses. Until we have that there's no way to actually display the results.
Once we have that, and we're ready to implement search, I think there is a low hanging fruit that can give us immediate results before implementing full text search.
The use case of searching via a partial address (e.g., show me every transaction that starts with 0xabc32...) is less often used. An easier thing to implement and one that would give a lot of benefit to users would be simply to allow searching via exact address / block number / transaction hash.
So when someone enters something in the search box, we can just understand from the length and structure of the string whether it is a transaction hash, a block number, or an address, and then simply send the user to the url for that particular tx/block/address.
Again, this can only be implemented once we have those pages.
Provide search functionality in Xplore and CLI
Abstract
Currently Xplore does not return search results or provide any view when searching. Implementation of search can be exposed in the Xplore dashboard as well as the CLI as an added bonus.
Motivation
Currently Xplore is lacking the functionality.
Proposal
We can use a hosted solution and also expose this to the CLI. Elastic Search, Algolia, etc can be chosen.
The text was updated successfully, but these errors were encountered: