Description

In order to facilitate better customization and flexibility in field layouts we should introduce new props that can be utilized by various data views layouts to determine how fields should be rendered. These props will allow data views layouts to decide whether or not to use it, providing more granular control over the presentation of fields.

Discussion Points

1. Purpose of the Prop:

   • Identify the prop that would effectively define the distinction in field rendering.
   • Examples of such props include size or isDetailed.

2. Implementation:

   • Data Views layouts can opt to use this prop to render fields differently.

3. Field Behavior:

   • Each field can then decide what it means for them to change size or to show details.
   • Some fields might determine that the prop has no impact on their rendering.

Expected Outcome

• Enhanced flexibility in field presentation.
• Consistent and customizable rendering logic across different layouts.

Next Steps

• Discuss potential prop options (size, isDetailed, etc.)
• Define how these props will be implemented and utilized within layouts.
• Determine the impact on existing fields and their default behaviors.

Reference

The original discussion can be found in the related thread #64496 (comment)