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 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.
It can be replaced with directory indexing.
The chrome extension will create initial search database by directory indexing.
Whenever a new update is made to the directories, it will be reflected in the database instantly after flushing the indexing file.
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.
The text was updated successfully, but these errors were encountered:
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.
FixesOpenGenus#70
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.
FixesOpenGenus#70
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.
This is a(n):
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.The text was updated successfully, but these errors were encountered: