Skip to content

Fix launcher clipboard parsing for GNOME file managers - #31

Merged
howdeploy merged 1 commit into
howdeploy:mainfrom
TroopJostle:feat/launcher-paste-project-path
Sep 7, 2026
Merged

Fix launcher clipboard parsing for GNOME file managers#31
howdeploy merged 1 commit into
howdeploy:mainfrom
TroopJostle:feat/launcher-paste-project-path

Conversation

@TroopJostle

Copy link
Copy Markdown
Contributor

GNOME clipboard payloads begin with a marker and a copy/cut verb, which the launcher previously selected as the project directory. Select the first path-looking line so these payloads resolve to the actual directory.

Follow-up to the review on #27, which has already merged. Extract the parser into src/renderer/src/lib/ and add behavioral coverage for GNOME copy/cut payloads, line endings, paired quotes, URI lists, Windows drive/UNC paths, percent-decoding, and invalid input.

Validation on 994e18b: npm test (542 passed), npm run typecheck, and npm run build all pass locally.

The optional home-directory expansion and paste-icon follow-ups remain deferred; no suitable paste icon exists in the vendored Lucide assets.

@howdeploy
howdeploy merged commit 7465bd7 into howdeploy:main Sep 7, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants