Skip to content

update settings and documentation for beta 26#162

Merged
Adammatthiesen merged 3 commits into
mainfrom
beta.26
Sep 5, 2025
Merged

update settings and documentation for beta 26#162
Adammatthiesen merged 3 commits into
mainfrom
beta.26

Conversation

@Adammatthiesen
Copy link
Copy Markdown
Member

@Adammatthiesen Adammatthiesen commented Sep 4, 2025

Description

  • Closes #
  • What does this PR change? Give us a brief description.

TODO BEFORE MERGE

  • Update packages to beta26 after they have been released.

Summary by CodeRabbit

  • Documentation
    • Added 0.1.0-beta.26 upgrade guide detailing breaking changes (DB schema migration required, middleware locals access changes), features, bug fixes, and migration examples.
    • Removed sidebar badge metadata from select docs for cleaner presentation.
  • Bug Fixes
    • SDK page lookup now returns undefined when not found; fixed form-data handling on first-time setup.
  • Chores
    • Dependency bumps to 0.1.0-beta.26, updated docs config, submodule pointer, and editor spell-check dictionary (added "Iconify").

@netlify
Copy link
Copy Markdown

netlify Bot commented Sep 4, 2025

Deploy Preview for studiocms-dev-docs ready!

Name Link
🔨 Latest commit e487b26
🔍 Latest deploy log https://app.netlify.com/projects/studiocms-dev-docs/deploys/68bac489a711130008108ebb
😎 Deploy Preview https://deploy-preview-162--studiocms-dev-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Sep 4, 2025

📝 Walkthrough

Walkthrough

Updates include a VS Code spell list entry, removal/addition of MDX frontmatter badges and a new upgrade guide, package dependency bumps, a studiocms submodule pointer update, and a reworked TypeDoc entryPoints list.

Changes

Cohort / File(s) Summary
Editor config
\.vscode/settings.json
Added "Iconify" to cSpell.words.
Docs: badge cleanup
src/content/docs/en/guides/upgrade/version-guides/0-1-0-beta-25.mdx, src/content/docs/en/how-it-works/effect.mdx
Removed sidebar.badge blocks from MDX frontmatter.
Docs: new upgrade guide
src/content/docs/en/guides/upgrade/version-guides/0-1-0-beta-26.mdx
Added 0.1.0-beta.26 upgrade guide with Breaking Changes (DB schema, Astro.locals scoping), Features, and Bug fixes; imports ReadMore, QuickUpdate, uses Aside.
TypeDoc config overhaul
typedoc.config.ts
Reworked entryPoints: consolidated handlers, removed legacy utils/handlers, added new utils/virtuals (e.g., stripIconify, virtual auth/i18n/sdk/mailer modules), reorganized documented surface.
Package deps
package.json
Bumped multiple @studiocms/* and studiocms dependencies from 0.1.0-beta.250.1.0-beta.26.
Submodule
studiocms
Updated submodule gitlink to a new commit (de2b4b9892991c95a4109d84961816dd82018ed2).

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Possibly related PRs

  • beta.25 docs #160 — Edits include TypeDoc entryPoints, package dependency bumps, and cSpell/documentation updates (high overlap).
  • Beta.22 docs #150 — Overlaps in TypeDoc configuration and documented module entry points.
  • Beta.24 docs #158 — Related changes to MDX frontmatter badges and submodule/package updates.

Suggested labels

i18n

Suggested reviewers

  • louisescher
  • RATIU5
  • dreyfus92

Poem

I nibble docs and hop with glee,
A badge removed, a guide set free.
Submodule pointer, packages climb,
TypeDoc trimmed—tidy in time.
Iconify added — spellings fine, rabbit cheers! 🐇✨


📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 19b4a9d and e487b26.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (2)
  • package.json (1 hunks)
  • studiocms (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • studiocms
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Run Starlight Link Check
🔇 Additional comments (3)
package.json (3)

34-34: @studiocms/ui remains unconstrained by 0.1.0-beta.26 packages – no change needed.


25-33: Ready to merge All StudioCMS 0.1.0-beta.26 packages are published on npm and pnpm-lock.yaml is already up-to-date.


37-41: Override ^6.3.4 matches Astro 5.12.9’s vite dependency — no adjustment needed.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch beta.26

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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore or @coderabbit ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@studiocms-no-reply
Copy link
Copy Markdown
Member

studiocms-no-reply commented Sep 4, 2025

Lunaria Status Overview

🌕 This pull request will trigger status changes.

Learn more

By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.

You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File Note
en/guides/upgrade/version-guides/0-1-0-beta-25.mdx Source changed, localizations will be marked as outdated.
en/guides/upgrade/version-guides/0-1-0-beta-26.mdx Localization added, will be marked as complete.
en/how-it-works/effect.mdx Source changed, localizations will be marked as outdated.
Warnings reference
Icon Description
🔄️ The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

@Adammatthiesen Adammatthiesen changed the title i18n(fr): update settings and documentation for beta 26 update settings and documentation for beta 26 Sep 4, 2025
@Adammatthiesen Adammatthiesen marked this pull request as ready for review September 4, 2025 20:09
@Adammatthiesen Adammatthiesen requested a review from a team as a code owner September 4, 2025 20:09
@coderabbitai coderabbitai Bot added the i18n label Sep 4, 2025
Copy link
Copy Markdown
Contributor

@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.

Actionable comments posted: 0

🧹 Nitpick comments (8)
.vscode/settings.json (1)

10-10: Consider adding lowercase alias to avoid case-sensitivity misses.

cSpell treats mixed-case entries as case-sensitive; if "iconify" appears in package names/URLs/code, it may still flag. Add the lowercase variant too.

Apply this diff:

     "genpkey",
     "Iconify",
+    "iconify",
     "inox",
studiocms (1)

1-1: Consider referencing a release tag or annotating the PR with the corresponding release.

If this SHA corresponds to beta.26, linking the tag or noting the release in the PR description helps traceability and bisects. Alternatively, track the submodule to a release branch/tag for easier maintenance.

src/content/docs/en/guides/upgrade/version-guides/0-1-0-beta-26.mdx (4)

13-15: Remove unused imports or put Aside to use.

ReadMore and Aside are imported but unused. Either remove them or add a callout that actually uses Aside.

Option A — remove unused imports:

-import ReadMore from '~/components/ReadMore.astro'
 import QuickUpdate from '~/components/QuickUpdate.astro'
-import { Aside } from '@astrojs/starlight/components'

Option B — keep Aside and add a DB backup callout (recommended for an upgrade guide):

 <QuickUpdate />
 
 ## Breaking Changes
@@
-- Updated Astro DB Table schema (Users will be required to run `astro db push --remote` to update their table schema)
+- Updated Astro DB table schema (Run `astro db push --remote` to apply schema changes)
+<Aside type="caution" title="Back up your database">
+Before running <code>astro db push</code> (local or with <code>--remote</code>), back up your DB. Schema changes are destructive if they drop or alter columns.
+</Aside>

21-24: Grammar, casing, and clarity nits in “Breaking Changes.”

Light edits for consistency and readability.

-- Updated Astro DB Table schema (Users will be required to run `astro db push --remote` to update their table schema)
-   - Implements new DB table for dynamic config storage in unified table.
-   - Updated AstroDB table config to utilize enums for permissions.
-- Remove deprecated locals from middleware in favor of a joined StudioCMS locals object.
+- Updated Astro DB table schema (Run `astro db push --remote` to apply schema changes).
+   - Implements a new unified DB table for dynamic config storage.
+   - Updated Astro DB table config to use enums for permissions.
+- Removed deprecated locals from middleware in favor of a unified StudioCMS locals object.

25-33: Fix “Astro.Locals” casing and tense; tighten phrasing.

Use Astro.locals (lowercase “l”) and keep past tense.

-   - Removed top-level Astro.Locals keys:
+   - Removed top-level Astro.locals keys:
@@
-   - New location:
-      - Access these under `Astro.locals.StudioCMS`.
+   - New location: access under `Astro.locals.StudioCMS`.
@@
-   - Renames:
+   - Renamed:

54-59: Tense and specificity in Features/Bug fixes (minor copy edits).

Keep past tense and tighten wording.

- - Update to `@studiocms/ui` 1.0 beta.
+ - Updated to `@studiocms/ui` 1.0 beta.
@@
-- Adjust SDK page lookup to return undefined when a page is not found, eliminating noisy Astro errors in development.
-- Fix form data conversion on first time setup.
+- Adjusted SDK page lookup to return `undefined` when a page is not found, reducing noisy Astro errors in development.
+- Fixed form-data conversion on first-time setup.

If downstream code previously assumed a thrown error or non-undefined return, please confirm this behavior change is non-breaking for your users and reflected in the API docs.

typedoc.config.ts (2)

168-168: New utility in docs surface: stripIconify.ts.

Looks fine; just confirm it’s intentionally part of the public doc surface and not an internal-only helper.


173-175: Potential duplication: documenting both auth/index.ts and auth/core.ts.

If auth/index.ts re-exports from auth/core.ts, listing both can create duplicate symbols/pages in TypeDoc. Prefer the aggregator entry point only.

Proposed change (if index re-exports core):

- getFilePathToPackage('studiocms', 'src/virtuals/auth/index.ts'),
- getFilePathToPackage('studiocms', 'src/virtuals/auth/core.ts'),
+ getFilePathToPackage('studiocms', 'src/virtuals/auth/index.ts'),
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between cb97d51 and 19b4a9d.

📒 Files selected for processing (6)
  • .vscode/settings.json (1 hunks)
  • src/content/docs/en/guides/upgrade/version-guides/0-1-0-beta-25.mdx (0 hunks)
  • src/content/docs/en/guides/upgrade/version-guides/0-1-0-beta-26.mdx (1 hunks)
  • src/content/docs/en/how-it-works/effect.mdx (0 hunks)
  • studiocms (1 hunks)
  • typedoc.config.ts (3 hunks)
💤 Files with no reviewable changes (2)
  • src/content/docs/en/guides/upgrade/version-guides/0-1-0-beta-25.mdx
  • src/content/docs/en/how-it-works/effect.mdx
🧰 Additional context used
🪛 LanguageTool
src/content/docs/en/guides/upgrade/version-guides/0-1-0-beta-26.mdx

[grammar] 13-13: There might be a mistake here.
Context: ...dMore from '
/components/ReadMore.astro' import QuickUpdate from '
/components/Qu...

(QB_NEW_EN)


[grammar] ~14-14: There might be a mistake here.
Context: ...te from '
/components/QuickUpdate.astro' import { Aside } from '@astrojs/starligh...

(QB_NEW_EN)


[grammar] ~22-~22: There might be a mistake here.
Context: ...dynamic config storage in unified table. - Updated AstroDB table config to utilize ...

(QB_NEW_EN)


[grammar] ~25-~25: There might be a mistake here.
Context: ... - Removed top-level Astro.Locals keys: - SCMSGenerator, SCMSUiGenerator, latestVersion, `s...

(QB_NEW_EN)


[grammar] ~26-~26: There might be a mistake here.
Context: ...tVersion, siteConfig, defaultLang, routeMap -userSessionData, emailVerificationEnabled, userPermi...

(QB_NEW_EN)


[grammar] ~28-~28: There might be a mistake here.
Context: ...el -wysiwygCsrfToken` (renamed) - New location: - Access these under...

(QB_NEW_EN)


[grammar] ~29-~29: There might be a mistake here.
Context: ...gCsrfToken(renamed) - New location: - Access these underAstro.locals.StudioC...

(QB_NEW_EN)


[grammar] ~32-~32: There might be a mistake here.
Context: ...neditorCSRFToken` (under StudioCMS) - Migration examples: - Before: ...

(QB_NEW_EN)


[grammar] ~33-~33: There might be a mistake here.
Context: ...nder StudioCMS) - Migration examples: - Before: ```ts const { ...

(QB_NEW_EN)

🔇 Additional comments (7)
.vscode/settings.json (1)

10-10: LGTM: Added "Iconify" to cSpell dictionary.

This prevents false positives in docs/editor. No issues with JSON structure or ordering.

studiocms (1)

1-1: Submodule bump verified. .gitmodules correctly points to https://github.com/withstudiocms/studiocms.git and commit d77a8c16c97b91343f1c03b2fd9dd2fca0252647 exists upstream. Ensure CI runs git submodule sync --recursive && git submodule update --init --recursive before merging.

src/content/docs/en/guides/upgrade/version-guides/0-1-0-beta-26.mdx (2)

36-41: Migration example (locals) looks good.

Clear before/after snippet; matches the bullet list above.


1-11: Unify version string in description
Change the description to “Upgrade StudioCMS to 0.1.0-beta.26”. The sidebar.badge.variant: success setting is valid (supported variants: note, danger, success, caution, tip, default).

typedoc.config.ts (3)

211-211: Add SDK config module to docs surface.

Good addition; aligns with the SDK reorg.


180-181: Old virtuals/i18n/index.ts reference removed
Search for virtuals/i18n/index.ts in typedoc.config.ts returned no occurrences; the old index entry is fully removed.


130-130: No stale changelog references remain — verified that typedoc.config.ts contains no references to handlers/changelog/index.ts or handlers/changelog/changelogLoader.ts.

@coderabbitai coderabbitai Bot added the i18n label Sep 5, 2025
@Adammatthiesen Adammatthiesen merged commit b38f93b into main Sep 5, 2025
12 checks passed
@Adammatthiesen Adammatthiesen deleted the beta.26 branch September 5, 2025 11:21
ArmandPhilippot added a commit to ArmandPhilippot/studiocms-docs that referenced this pull request Sep 8, 2025
dreyfus92 pushed a commit that referenced this pull request Sep 14, 2025
* i18n(fr): update docs for beta 26

See #162

* remove a frontmatter property

* fix casing
@coderabbitai coderabbitai Bot mentioned this pull request Sep 26, 2025
1 task
@coderabbitai coderabbitai Bot mentioned this pull request Oct 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants