From e407073c9e7ff984077c6a80cc10209b33b3ea5c Mon Sep 17 00:00:00 2001 From: Alvin Bryan <107407814+alvinometric@users.noreply.github.com> Date: Thu, 15 Jun 2023 08:40:32 -0700 Subject: [PATCH] Update error message for custom slugs in collection (#7395) Co-authored-by: Sarah Rainsberger --- packages/astro/src/core/errors/errors-data.ts | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/packages/astro/src/core/errors/errors-data.ts b/packages/astro/src/core/errors/errors-data.ts index 8139c0fcd..a47087336 100644 --- a/packages/astro/src/core/errors/errors-data.ts +++ b/packages/astro/src/core/errors/errors-data.ts @@ -1042,9 +1042,9 @@ See https://docs.astro.build/en/guides/server-side-rendering/ for more informati /** * @docs * @see - * - [The reserved entry `slug` field](https://docs.astro.build/en/guides/content-collections/) + * - [The reserved entry `slug` field](https://docs.astro.build/en/guides/content-collections/#defining-custom-slugs) * @description - * A content collection schema should not contain the `slug` field. This is reserved by Astro for generating entry slugs. Remove the `slug` field from your schema, or choose a different name. + * A content collection schema should not contain the `slug` field. This is reserved by Astro for generating entry slugs. Remove `slug` from your schema. You can still use custom slugs in your frontmatter. */ ContentSchemaContainsSlugError: { title: 'Content Schema should not contain `slug`.',