Directory indexing for creating search database

[AasthaGupta]

This is a(n):

• [x] New feature proposal
• [ ] Reporting a keyword
• [ ] Error
• [ ] Proposal to the Search Engine
• [x] Other

Details:

Currently all the search database is stored in obj. All the search entries are hard-coded in popup.js. It seems both unscalable and tedious to maintain for large search entries.

1. It can be replaced with directory indexing.
2. The chrome extension will create initial search database by directory indexing.
3. Whenever a new update is made to the directories, it will be reflected in the database instantly after flushing the indexing file.
4. This will ease the process of updating search entries because now we don't have to maintain a hard-coded database and a simple update in the directory will be enough.

[AasthaGupta]

@AdiChat I'd like to know about your opinions on this idea. I'd be happy to discuss it. :)

[AdiChat]

Sounds good.

The code needs refactoring. In the current scenario, we generate the metadata (that is obj) through Cosmos-Search. Changes in the directory will break it but it is unlikely that a user will do so. Still, having an update system will be a nice and safe feature to have.