Skip to content
This repository was archived by the owner on Sep 1, 2024. It is now read-only.
This repository was archived by the owner on Sep 1, 2024. It is now read-only.

Decide how to handle multiple matches #3

@ccryx

Description

@ccryx

When querying information for a given url, the server can return multiple matches (e.g. when multiple entries for the same url exist or a regular expression was used that resulted in multiple matches).
This is fine for interactive usage: just print all the entries.
For script usage there are multiple ways to handle this:

  • let the script handle it: possible but also possibly adding unnecessary complexity when using the output of the command directly in applications that don't support any fancy scripting.
  • let the user handle it: the user would have to create entries with unique url fields if they only want one match and select for that one specifically. If they want multiple matches they could use a regex. This would break usage with chromeIPass/passIFox and/or lead to redundant entries in the database.
  • let the user specify additional matching parameters. There could be a --match option. Usage could be in the form of --match name|login|uuid=<string>|regex. In the long run this is probably the best solution.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions