-
Notifications
You must be signed in to change notification settings - Fork 3
Define relevancy APIs for exposing data #17
Comments
@linuxwolf @jimporter given we first need lock/unlock #6 how confident do you feel about building search as part of Alpha? |
It'd be pretty easy to make a super-simple search interface for alpha. |
It should be fairly easy to do a basic "substring" search over title and username, all in the "./manage" view. |
for possible inspiration, or a base: https://github.com/enkidevs/react-search-input |
Added a front-end issue for search interface: Talked with @linuxwolf and this items purpose should be more around a 'search the page and send back relevant data' API, for lack of better words right now. |
As an initial implementation, I was planning on doing all this in the front-end. It would probably be best to put it in the backend eventually, but that adds some complexity to the data synchronization that I don't want to get into for alpha. |
Updated the description to limit its scope. This functionality something that can only really be done in the back-end. |
Oh, right. That's a bit different than the question Devin was asking me. Still, it might make sense to have search in the backend too. We can discuss that elsewhere, though. |
Given where we're initially going with autofill mozilla-lockwise/lockbox-extension#467, moving this back to the inbox for now. |
The purpose of this API is to allow a content script to check if the datastore might have credentials for the current web page.
The API should take the URL, and return back some sort of indication there is (or is not) at least one relevant item. The implementation should not require the datastore to be unlocked in order to return positive results.
The text was updated successfully, but these errors were encountered: