raycast / raycast/extensions

[KeePassXC] References wont get resolved

Open
#17,560 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug Dont close extension extension: keepassxc Stale status: stalled
Dominant language
TypeScript
Stars
7.8k
Forks
6.9k
Avg merge
2d 6h
Merged PRs (30d)
442

Description

Extension

https://www.raycast.com/pabroux/keepassxc

Raycast Version

1.5.4

macOS Version

15.3.1

Description

Hello!

Since the overhaul of this extension in #16143 references wont get resolved anymore.

In this PR the retrieval got updated to use keepassxc-cli export -f csv to get all entries. This has the flaw, that reference fields won't get resolved anymore.
Before this change keepassxc-cli show was used, wich resolves references.

This problem is most relevant for the fields username and password.

Steps To Reproduce
  1. Open KeePassXC and load Database that is used with Raycast Extension.
  2. Create entry with a title, username and password.
  3. Clone entry from step 2 and select Replace username and password with references
  4. Open Raycast and got to Extension KeePaassXC
  5. Search for the cloned entry from step 3.
  6. Paste username and password in to text file.
Current Behaviour

References don't get solved, so the output is in the following formats.

Passwords: {REF:P@I:*}
Usernames: {REF:U@I:*}

Expected Behaviour

References get resolved and the output are values from the referenced entry (Step 2 from the "Steps to reproduce").

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the KeePassXC extension changes in PR #16143 and compare the use of keepassxc-cli export -f csv with the earlier keepassxc-cli show behavior. Reproduce the reference case from the listed steps, then verify that the cloned entry returns resolved username and password values rather than {REF:U@I:*} and {REF:P@I:*}.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.