Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve error for invalid content field #1365

Merged
merged 1 commit into from
Nov 28, 2024

Conversation

emmatown
Copy link
Member

Fixes #1320

Copy link

changeset-bot bot commented Nov 28, 2024

🦋 Changeset detected

Latest commit: 3473697

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 13 packages
Name Type
@keystatic/core Patch
@keystar/docs Patch
@example/astro-content Patch
@example/astro Patch
@example/localization Patch
@example/next-app Patch
@example/next-block-builder Patch
@example/next-pages Patch
@keystatic/remix-test-app Patch
keystatic-docs Patch
@keystatic/templates-astro Patch
@keystatic/templates-nextjs Patch
@keystatic/templates-remix Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@emmatown emmatown force-pushed the improve-error-for-invalid-content-field branch from 472e7eb to 3473697 Compare November 28, 2024 02:22
@emmatown emmatown merged commit c65f48b into main Nov 28, 2024
8 checks passed
@emmatown emmatown deleted the improve-error-for-invalid-content-field branch November 28, 2024 02:39
@github-actions github-actions bot mentioned this pull request Nov 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unclear error message if <collection>.format.contentField doesn't exist
1 participant