Update zotero extension

[ridemountainpig]

Description

Add "Open PDF in System Viewer" action to open the attachment with the system's default viewer. Close #26817.

Screencast

Checklist

• I read the extension guidelines
• I read the documentation about publishing
• I ran npm run build and tested this distribution build in Raycast
• I checked that files in the assets folder are used by the extension itself
• I checked that assets used in the README are located outside the metadata folder if they were not generated with our metadata tool

[raycastbot]

Thank you for your contribution! 🎉

🔔 @sadanand-singh @lazarjov @joshuahhh @faridrashidi you might want to have a look.

You can use this guide to learn how to check out the Pull Request locally in order to test it.

📋 Quick checkout commands

BRANCH="zotero"
FORK_URL="https://github.com/ridemountainpig/extensions.git"
EXTENSION_NAME="zotero"
REPO_NAME="extensions"

git clone -n --depth=1 --filter=tree:0 -b $BRANCH $FORK_URL
cd $REPO_NAME
git sparse-checkout set --no-cone "extensions/$EXTENSION_NAME"
git checkout
cd "extensions/$EXTENSION_NAME"
npm install && npm run dev

We're currently experiencing a high volume of incoming requests. As a result, the initial review may take up to 10-15 business days.

[greptile-apps]

Greptile Summary

This PR adds an "Open PDF in System Viewer" action to the Zotero extension, allowing users to open PDF attachments with the macOS system's default viewer instead of routing everything through Zotero. A new resolveAttachmentPath helper correctly handles both Zotero-stored attachments (resolving storage:<filename> paths to <zotero_dir>/storage/<key>/<filename>) and linked-file attachments. All three concerns raised in the previous review cycle have been addressed: resolveHome is now imported from zoteroApi.ts rather than duplicated, open() is wrapped in a try/catch with a user-facing HUD error, and attachmentFilePath is computed once per item and reused. The CHANGELOG entry is correctly placed at the top with a {PR_MERGE_DATE} placeholder.

• New resolveAttachmentPath() function using the existing resolveHome utility from zoteroApi.ts
• "Open PDF in System Viewer" action using Raycast's open() API with proper try/catch error handling and showHUD feedback
• attachmentFilePath computed once outside JSX and reused in both the render condition and onAction callback
• Changelog entry added with standard {PR_MERGE_DATE} placeholder at the top in descending version order
• Minor: the new action is placed second in the action list rather than appended to the end, which is a style note that does not affect functionality

Confidence Score: 5/5

Safe to merge — all prior P1 concerns resolved; one minor P2 action-ordering note remains that does not affect functionality

All three previously-raised P1 concerns have been fully addressed: resolveHome is reused from zoteroApi.ts instead of duplicated, open() has error handling with showHUD, and attachmentFilePath is computed once per item and reused. The only remaining finding is a P2 style note about action panel ordering which does not impact correctness, user data, or the primary use case.

No files require special attention

Important Files Changed

Filename	Overview
extensions/zotero/src/common/View.tsx	Adds resolveAttachmentPath helper and 'Open PDF in System Viewer' action with proper error handling and single path computation per item
extensions/zotero/CHANGELOG.md	Adds changelog entry for the new feature with correct {PR_MERGE_DATE} placeholder correctly placed at the top

Prompt To Fix All With AI

This is a comment left during a code review.
Path: extensions/zotero/src/common/View.tsx
Line: 263-278

Comment:
**New action inserted mid-list instead of appended to the end**

Per the extension guidelines, new action panel actions should be appended to the end of the list rather than inserted in the middle. The "Open PDF in System Viewer" action is currently placed as the second action (right after "Open PDF"), before "Open in Zotero" and all the other existing actions.

Consider moving it to just before the `ActionPanel.Section` block so the established action order isn't disrupted and users aren't surprised by keyboard-shortcut shifts on existing actions.

**Rule Used:** What: New action panel actions should be appended ... ([source](https://app.greptile.com/review/custom-context?memory=cde63d3f-214c-4294-9a2a-bb8323ef7d33))

How can I resolve this? If you propose a fix, please make it concise.

_{Greploops — Automatically fix all review issues by running /greploops in Claude Code. It iterates: fix, push, re-review, repeat until 5/5 confidence.
Use the Greptile plugin for Claude Code to query reviews, search comments, and manage custom context directly from your terminal.}

_{Reviews (2): Last reviewed commit: "Update zotero extension" | Re-trigger Greptile}

[ridemountainpig]

@greptile-apps please review again.

[pernielsentikaer]

Looks good to me, approved 🔥

[github-actions]

Published to the Raycast Store:
https://raycast.com/reckoning-dev/zotero

[raycastbot]

🎉 🎉 🎉

We've rewarded your Raycast account with some credits. You will soon be able to exchange them for some swag.