Make Raycast API `Applications` object return a Windows path as well.

Open
#22,147 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
api, desktop

Research direction

Start by reviewing the getApplications() entry point and the Applications object documented in the Raycast API reference. Reproduce the Windows result described for KeePassXC and trace how path and windowsAppId are populated. Done means Applications objects expose a valid Windows application path that extensions can use to locate installed tools.

Written by the indexing model from the issue text.

Description

api feature request Stale
Description

Hello there 👋🏻,

The Raycast API provides a getApplications() function to retrieve an existing application and some of its metadata. More precisely, it returns a list of Applications objects (here is the doc). Currently, Applications does not return valid paths on Windows unlike on macOS.

For an extension https://github.com/raycast/extensions/pull/22073#discussion_r2421579206, we want to retrieve a CLI installed with a software. The CLI and the software are both in the same folder:

  • C:\Program Files\KeePassXC\keepassxc-cli.exe
  • C:\Program Files\KeePassXC\keepassxc.exe

Here is what we get from a getApplications call on Windows:

[
  {
    name: 'KeePassXC',
    localizedName: undefined,
    path: '/Applications/8570d9f0-9729-57a6-89cc-06429aab905e',
    windowsAppId: '/Applications/8570d9f0-9729-57a6-89cc-06429aab905e'
  }
]

So, if I get it correctly, the path should be a kind of symbolic link to the keepassxc.exe. Is there a built-in way in Raycast API (or planned) to have the Windows path?

Who will benefit from this feature?

Everyone trying to retrieve installed tools/application on Windows.

Anything else?

No response

Dominant language
TypeScript
Stars
7.8k
Forks
6.9k
Avg merge
2d 3h
Merged PRs (30d)
447

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.

More from raycast/extensions

All issues in raycast/extensions

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.