claude/clever-raman-a8f9b4#96
Merged
Merged
Conversation
BREAKING-CHANGE: use new API for nuxt-content v3
BREAKING-CHANGE: use new API for nuxt-content v3
Complete the queryContent (v2) → queryCollection (v3) migration across all remaining pages and components. Fix content not rendering due to missing wasm-unsafe-eval CSP directive (required for browser-side WebAssembly SQLite) and missing custom frontmatter fields in the content schema. Changes: - components/ArticleContent.vue, ContentPreview.vue, TextPreviewBox.vue: migrate to queryCollection, fix null-safety, fix ContentRenderer v3 API - pages/activities.vue, blog.vue, collaborations.vue, database/index.vue, glossary/index.vue: migrate queryContent → queryCollection - content.config.ts: add heading, image, caption, captionLink, subheading, img, route fields to schema so they are first-class SQLite columns - nuxt.config.ts: add wasm-unsafe-eval to CSP script-src for WebAssembly SQLite support; add routeRules to bypass security middleware on /__nuxt_content/** API routes; upgrade @nuxtjs/i18n to v9 (fixes unhead v2 incompatibility); fix swapped locale names (de/en) - package.json / pnpm-lock.yaml: update @nuxtjs/i18n to ^9.5.6 - .gitignore: exclude /.data/ (runtime SQLite database) - .data/content/contents.sqlite: untrack from git (runtime-generated file) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Complete Nuxt Content v3 migration and fix content rendering
- Fix members query to use LIKE prefix match instead of exact path match - Fix useAsyncData key to use template literal for proper interpolation - Rename loop variable from 'index' to 'i' to avoid conflict with index data ref - Update data access patterns from v2 (members.data.value) to v3 (members) - Update path field from _path to path - Remove debug template code and old commented-out v2 declarations Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Sort by stem instead of path so that the numeric file prefixes (1.susanne-hochreiter, 2.marina-rauchenbacher, ...) determine display order. The path column strips these prefixes, causing alphabetical-by-name ordering instead of the intended sequence. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…ude/clever-raman-a8f9b4
The project was migrated from npm to pnpm, but the GitHub Actions workflows still had Setup Node.js / npm ci steps referencing the non-existent package-lock.json. These steps caused the workflow to fail because npm ci requires a package-lock.json. The Docker build is self-contained (Dockerfile uses corepack + pnpm), so the host-side install steps were always redundant and are removed. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.