You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe
For the development of the new website for the 3D printing conference Printed-Amsterdam, I chose Nuxt3 with @nuxt/content in combination with NuxtStudio. This setup is intended to provide an intuitive and user-friendly experience, especially for non-technical users.
However, during the creation of the data schema, two fundamental missing features became apparent:
It would be extremely helpful to support relationships between collections. Since @nuxt/content v3 now uses an underlying SQLite database, this should be more feasible than in previous versions.
As a practical example, in the current project, a talk can be given by one or more speakers. This scenario requires a many-to-many relationship. It would be ideal if such relationships could be defined in both directions, but even a basic one-way reference would unlock a wide range of powerful use cases - especially since reverse querying is still possible with a bit of logic.
Describe alternatives you've considered
Currently, the only workaround is to manually create slugs and reference them across collections without any form of validation during build time. This approach is inconvenient and error-prone, making @nuxt/content projects difficult to scale.
Alternatively, switching to another headless CMS is possible, but that would mean leaving the Nuxt ecosystem. However, relationships between collections are a basic feature required by many projects beyond simple blogs.
Additional context
This would be a great enhancement for NuxtStudio in particular, as it could provide a searchable dropdown field for linking entries from another collection.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe
For the development of the new website for the 3D printing conference Printed-Amsterdam, I chose Nuxt3 with @nuxt/content in combination with NuxtStudio. This setup is intended to provide an intuitive and user-friendly experience, especially for non-technical users.
However, during the creation of the data schema, two fundamental missing features became apparent:
type == data
schema are not being validated (see feat(content): support data schema validation on build #3351 ).The project is available as an open-source repository for the community:
https://github.com/toddeTV/printed-amsterdam.com
Describe the solution you'd like
It would be extremely helpful to support relationships between collections. Since @nuxt/content v3 now uses an underlying SQLite database, this should be more feasible than in previous versions.
As a practical example, in the current project, a talk can be given by one or more speakers. This scenario requires a many-to-many relationship. It would be ideal if such relationships could be defined in both directions, but even a basic one-way reference would unlock a wide range of powerful use cases - especially since reverse querying is still possible with a bit of logic.
Describe alternatives you've considered
Currently, the only workaround is to manually create slugs and reference them across collections without any form of validation during build time. This approach is inconvenient and error-prone, making @nuxt/content projects difficult to scale.
Alternatively, switching to another headless CMS is possible, but that would mean leaving the Nuxt ecosystem. However, relationships between collections are a basic feature required by many projects beyond simple blogs.
Additional context
This would be a great enhancement for NuxtStudio in particular, as it could provide a searchable dropdown field for linking entries from another collection.
The text was updated successfully, but these errors were encountered: