fix(collection table): support conditional fields in columns schema

[Punith1117]

Summary

This PR fixes two issues when using fields.conditional() in collection columns:

1. Conditional fields were rejected by TypeScript when referenced in a collection's columns array.
2. Conditional field values were rendered as [object Object] in the collection list view.

Changes

TypeScript support

Updated the collection() column type definition to allow ConditionalField entries in addition to the previously supported field types.

Runtime rendering

When rendering collection table values, conditional field values are now detected and their discriminant value is displayed instead of coercing the entire object to a string.

Before:
[object Object]

After:
true or false

(or the selected discriminant value for select-based conditional fields).

Testing

Tested with conditional fields using:

• Checkbox discriminants (true / false)
• Select discriminants with multiple options

Verified that:

• Conditional fields can be added to columns without TypeScript errors.
• Collection list views render the selected discriminant value instead of [object Object].
• Existing supported column types continue to behave as before.

Implementation Notes

While investigating this issue, it became apparent that collection column rendering currently assumes that all column values have a scalar preview representation.

Conditional fields are one of the first structured field types where this assumption breaks. Their stored value is an object, which results in [object Object] being rendered when the value is coerced to a string.

For this fix, the conditional field's discriminant value is used as the column preview because it provides a meaningful scalar representation of the selected condition.

More generally, it may be safer for collection columns to explicitly support only scalar-like field types (and other field types that provide a well-defined preview value) rather than attempting to stringify arbitrary complex structures such as object, image, file, markdoc, or mdx fields.

A more comprehensive long-term solution could be a field-level preview resolver that allows each field type to define how it should be represented in collection columns. However, that appears to be a broader design change and is outside the scope of this PR.

Related

Fixes #1396

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0e5c6c9

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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