[douwepausma]

Description

Update of the Strapi extension with bug fixes, new features and up-to-date dependencies.

New

• Entries and media files load page by page, so large collections are no longer cut off at Strapi's maxLimit
• Search entries and media files on the server
• Filter entries by draft/published status and locale
• Entry details panel (⌘D) with actions to copy the document ID, API URL and JSON
• "Copy Markdown" and "Copy File ID" actions in the media library
• Clear error messages (HTTP status + Strapi's message) with a shortcut to the extension preferences

Fixes

• "Open in Strapi" for single types opened the wrong admin page
• Media URLs from upload providers like S3 and Cloudinary were broken
• Entry titles could crash or show [object Object] for empty, relation or rich text fields
• Empty media fields showed "null", and non-image files got a broken preview
• A host with a trailing slash produced invalid URLs

Maintenance

• Updated to @raycast/api 2.x, React 19 types, ESLint flat config and TypeScript 6
• Removed node-fetch and unused code

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 by the README are placed outside of the metadata folder

[raycastbot]

Thank you for the update! 🎉

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

[greptile-apps]

Confidence Score: 4/5

[Medium impact] The changes affect entry and media browsing in this Strapi extension.

Restore the required changelog placeholder before merging.

Findings

1.  Release date is hardcoded ▶

Fix with agent prompt

### Issue 1
extensions/strapi-raycast-extension/CHANGELOG.md:3
The new changelog heading replaces `{PR_MERGE_DATE}` with `2026-10-31`. The repository requires new entries to keep the placeholder so the release date is set when the PR merges. Restore `{PR_MERGE_DATE}` before merging.

```suggestion
## [Improvements] - {PR_MERGE_DATE}
```

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

The PR adds paged loading, server-side search, entry filters, detail views, and media actions.

• Entry lists search and filter results and show useful details.
• The media library searches files and offers useful file actions.
• Strapi links use the right host and admin page, with clearer errors.
• Entry titles and subtitles show readable text from content fields.
• The extension’s development setup and type files move to newer versions.

_{Reviews (3) · Last reviewed commit: "Update CHANGELOG.md, add platforms field..." · Reviewed by Greptile}

[0xdhrv]

Looks good to me, approved ✅

[github-actions]

Published to the Raycast Store:
https://raycast.com/douwepausma/strapi-raycast-extension

[raycastbot]

🎉 🎉 🎉

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

[greptile-apps]

Release date is hardcoded

The new changelog heading replaces {PR_MERGE_DATE} with 2026-10-31. The repository requires new entries to keep the placeholder so the release date is set when the PR merges. Restore {PR_MERGE_DATE} before merging.

Suggested change

	## [Improvements] - 2026-10-31
	## [Improvements] - {PR_MERGE_DATE}

Rule Used: What: Changelog entries must use {PR_MERGE_DATE} placeholder in titles, be placed at the top of the file, and maintain descending version order. Why: Standardized placeholders and consistent ordering ensure changelogs are maintainable and merge da... (source)

Prompt To Fix With AI

This is a comment left during a code review.
Path: extensions/strapi-raycast-extension/CHANGELOG.md
Line: 3

Comment:
**Release date is hardcoded**

The new changelog heading replaces `{PR_MERGE_DATE}` with `2026-10-31`. The repository requires new entries to keep the placeholder so the release date is set when the PR merges. Restore `{PR_MERGE_DATE}` before merging.

```suggestion
## [Improvements] - {PR_MERGE_DATE}
```

**Rule Used:** What: Changelog entries must use `{PR_MERGE_DATE}` placeholder in titles, be placed at the top of the file, and maintain descending version order.  Why: Standardized placeholders and consistent ordering ensure changelogs are maintainable and merge da... ([source](https://app.greptile.com/-/switch-tenant?tenant=raycast&next=%2Fcustom-context%3Fmemory%3Dc2214c11-df56-490a-b1c0-09a385df481a))

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!