06debf5e14
Fixes https://github.com/payloadcms/payload/issues/11224 Fixes https://github.com/payloadcms/payload/issues/10492 This PR fixes a few weird behaviours when `validate: true` is set on drafts: - when autosave is on and you submit an invalid form it would get stuck in an infinite loop - PreventLeave would not trigger for submitted but invalid forms leading to potential data loss Changes: - Adds e2e tests for the above scenarios - Adds a new `isValid` flag on the `Form` context provider to signal globally if the form is in a valid or invalid state - Components like Autosave will manage this internally since it manages its own submission flow as well - Adds PreventLeave to Autosave too for when form is invalid meaning data hasn't been actually saved so we want to prevent the user accidentally losing data by reloading or closing the page The following tests have been added 
22 lines
392 B
TypeScript
22 lines
392 B
TypeScript
import type { CollectionConfig } from 'payload'
|
|
|
|
import { draftWithValidateCollectionSlug } from '../slugs.js'
|
|
|
|
const DraftsWithValidate: CollectionConfig = {
|
|
slug: draftWithValidateCollectionSlug,
|
|
fields: [
|
|
{
|
|
name: 'title',
|
|
type: 'text',
|
|
required: true,
|
|
},
|
|
],
|
|
versions: {
|
|
drafts: {
|
|
validate: true,
|
|
},
|
|
},
|
|
}
|
|
|
|
export default DraftsWithValidate
|