fix fields validation to include field presets

[azrikahar]

Fixes #10854

• Requires Setting multiple field presets for role not working #10782 to be resolved first

Bug

Field presets are not taken into account during validation. Even though the field is already filled by preset, the form returns value is required:

Investigation

During the validation process, fields.value are checked with conditions and if default value isNil:

directus/app/src/composables/use-item/use-item.ts

Lines 326 to 337 in 8cdb6ed

	const fieldsWithConditions = fields.value.map((field) => applyConditions(item, field));
	const requiredFields = fieldsWithConditions.filter((field) => field.meta?.required === true);
	for (const field of requiredFields) {
	if (isNew.value === true && isNil(field.schema?.default_value)) {
	validationRules._and.push({
	[field.field]: {
	_submitted: true,
	},
	});
	}

However fields.value came from useCollection:

directus/app/src/composables/use-item/use-item.ts

Line 39 in 8cdb6ed

const { info: collectionInfo, primaryKeyField, fields } = useCollection(collection);

Which does not have field presets merged as default values. Fields with presets are returned from usePermission instead:

directus/app/src/composables/use-permissions.ts

Lines 73 to 87 in 8cdb6ed

	if (permissions.presets) {
	fields = fields.map((field: Field) => {
	if (field.field in permissions.presets!) {
	field.schema = {
	...(field.schema || {}),
	default_value: permissions.presets![field.field],
	} as any;
	}
	return field;
	});
	}
	return fields;
	});

Solution

---

This PR requires #10782 to be fixed first, due to the presets wrongly parsed as filter syntax. That causes it to be interpreted as creating a new relational item instead:

[krwrang]

I hope you can get this one out now since #10782 was closed and released. This has blocked our progress for long enough.