Duplicate files when part of two collections

[BenjaminOddou]

Hello,

It seems that YAML files (e.g., .navigation.yml) are loaded twice, probably because of the numbering.

EDIT: The content of the files is not loaded (content is empty)

[larbish]

Can you share your content.config.ts file? It might be because your file is loaded in two different collections

[BenjaminOddou]

Hello @larbish, indeed, my navigation files are both in nav and blog collections in the above case. I created the nav collection in order to modify the form fields in studio.

import type { z as zd } from 'zod'
import { defineCollection, defineContentConfig, z } from '@nuxt/content'

const iconLibraries = ['vscode-icons', 'simple-icons', 'lucide']

const AccessControlObject = z.object({
  users: z.array(z.string()).optional(),
  groups: z.array(z.string()).optional(),
})

export const AuthSchema = z.object({
  read: AccessControlObject.optional(),
  write: AccessControlObject.optional(),
}).optional()

export const DocsSchema = z.object({
  uid: z.string().editor({ hidden: true }),
  navigation: z.object({
    title: z.string().optional(),
    icon: z.string().editor({ input: 'icon', iconLibraries }).optional(),
  }).optional(),
  links: z.array(z.object({
    label: z.string(),
    icon: z.string().editor({ input: 'icon', iconLibraries }).optional(),
    to: z.string(),
    target: z.string().optional(),
  })).optional(),
  authors: z.array(z.string()).optional(),
  date: z.union([
    z.literal('auto'),
    z.coerce.date(),
  ]).default('auto'),
  draft: z.boolean().default(false).optional(),
  auth: AuthSchema,
})

export const BlogSchema = z.object({
  uid: z.string().editor({ hidden: true }),
  navigation: z.object({
    title: z.string().optional(),
    icon: z.string().editor({ input: 'icon', iconLibraries }).optional(),
  }).optional(),
  image: z.object({
    src: z.string().editor({ input: 'media' }),
    alt: z.string().optional(),
  }).optional(),
  authors: z.array(z.string()).optional(),
  date: z.string().date().optional(),
  draft: z.boolean().default(false).optional(),
  badge: z.enum(['Tutoriel', 'Annonce', 'Article']).optional(),
  auth: AuthSchema,
})

export type Blog = zd.infer<typeof BlogSchema>
export type Docs = zd.infer<typeof DocsSchema>

export default defineContentConfig({
  collections: {
    nav: defineCollection({
      type: 'data',
      source: {
        include: '**/*.navigation.yml',
      },
      schema: z.object({
        title: z.string(),
        description: z.string().optional(),
        icon: z.string().editor({ input: 'icon', iconLibraries }).optional(),
        to: z.string().optional(),
      }),
    }),
    docs: defineCollection({
      type: 'page',
      source: {
        include: '1.docs/**',
      },
      schema: DocsSchema,
    }),
    blog: defineCollection({
      type: 'page',
      source: {
        include: '2.blog/**',
      },
      schema: BlogSchema,
    }),
  },
})

[larbish]

First of all, overriding .navigation.yml collection won't work since nav files are internal files used by Content to provide metadata (the override won't work).

However, this make us realise we should raise an issue on Content side if a file is part of two collections since it's an anti pattern. I've created an issue on Nuxt Content .

What is the behaviour you would like to get by doing this @BenjaminOddou ?

---

I don't think this behaviour should be handled on Nuxt Studio side but let's keep a trace of a potential solution:

Since tree file is based on fsPath, if a file is detected twice in build tree (two collections), we can add it only once with special key or status warn and we can display it in readonly mode with a warning for the user.

IMO we should not "merge" both file and let it work as usual since it might raise concerns about wrong schema being applied (wrong collection).

[BenjaminOddou]

What is the behaviour you would like to get by doing this @BenjaminOddou ?

I intended to set the fields of the (old) Nuxt Studio form to match the properties defined in the nav collection, while still keeping these navigation files inside the docs and blog collections (which are used in my composables).

I will remove this nav collection for now, as it was more a workaround than an actual stable solution. However, I anticipate encountering this issue again once the YAML/Frontmatter form functionality is implemented.