Skip to content

Add directus-sdk#1457

Open
matt-rolley wants to merge 4 commits intonuxt:mainfrom
matt-rolley:add-directus-sdk
Open

Add directus-sdk#1457
matt-rolley wants to merge 4 commits intonuxt:mainfrom
matt-rolley:add-directus-sdk

Conversation

@matt-rolley
Copy link
Copy Markdown

Adds directus-sdk to the catalogue.

A Nuxt 4 module that wraps @directus/sdk v21 directly — built-in session-based authentication, realtime subscriptions, file management (@nuxt/image integration), type generation from your Directus schema, and @directus/visual-editing support.

Differentiator from the existing directus entry: that one is intevel/nuxt-directus, a custom abstraction over the Directus REST API. This module wraps the official @directus/sdk package directly, so everything the SDK exposes (readers, writers, realtime, auth) is available as an auto-import without going through a wrapper layer. Different target user, different API surface.

Links

Category CMS. Type 3rd-party.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 22, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 45359217-0598-4e91-a27b-29bb920fd64c

📥 Commits

Reviewing files that changed from the base of the PR and between 7f07c75 and fde7a2c.

📒 Files selected for processing (1)
  • modules/directus-sdk.yml
✅ Files skipped from review due to trivial changes (1)
  • modules/directus-sdk.yml

📝 Walkthrough

Walkthrough

A new module metadata manifest was added at modules/directus-sdk.yml. The manifest sets identifying fields (name, description, repository, npm package, icon), external links (GitHub, website, learn more), classification (category: CMS, type: 3rd-party), two maintainer GitHub identities, and Nuxt compatibility constraints indicating support for ^3.0.0 || ^4.0.0 with compatibility.requires: {}.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title 'Add directus-sdk' directly and clearly describes the main change: adding a new module manifest for the directus-sdk Nuxt module to the catalogue.
Description check ✅ Passed The description is directly related to the changeset, explaining why directus-sdk is being added, its features, how it differs from the existing directus module, and providing relevant links.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
Review rate limit: 7/8 reviews remaining, refill in 7 minutes and 30 seconds.

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
modules/directus-sdk.yml (1)

10-10: Consider pointing learn_more to module-specific docs.

On Line 10, learn_more currently targets Directus core docs. For catalog UX, linking to the module docs (same as website) is usually more actionable for users evaluating this Nuxt module.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@modules/directus-sdk.yml` at line 10, The learn_more field currently points
to the Directus core docs; update the learn_more YAML key to reference the
module-specific documentation (use the same URL as the website key) so users
evaluating the Nuxt module land on the module docs rather than core Directus
docs; locate the learn_more key in modules/directus-sdk.yml and replace its
value with the URL used by the website key.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@modules/directus-sdk.yml`:
- Line 10: The learn_more field currently points to the Directus core docs;
update the learn_more YAML key to reference the module-specific documentation
(use the same URL as the website key) so users evaluating the Nuxt module land
on the module docs rather than core Directus docs; locate the learn_more key in
modules/directus-sdk.yml and replace its value with the URL used by the website
key.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 43dd80cf-bce3-4d95-a661-105472f0e6a1

📥 Commits

Reviewing files that changed from the base of the PR and between da52820 and 67a1a04.

⛔ Files ignored due to path filters (1)
  • icons/directus-sdk.svg is excluded by !**/*.svg
📒 Files selected for processing (1)
  • modules/directus-sdk.yml

Comment thread modules/directus-sdk.yml Outdated
Co-authored-by: kheiner <heiner@heiner.work>
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