You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A user must currently specify their own icon when using FieldLabel. This makes it awkward to use with AutoField, as the user has to redefine the icons for their field type.
Proposals
Proposal 1
Add a fieldIcons export that maps the nodes to the field types. We should also use these internally to ensure consistency.
constfieldIcons={text: <Headingsize="16"/>}
The user can then use them alongside the FieldLabel API
And depending on the type you would show the proper icon.
If the user don't provide the type then he should provide his own icon and ofc his icon has the priority over the puck icons incase he provide the type and the icon at the same time
A user must currently specify their own icon when using FieldLabel. This makes it awkward to use with AutoField, as the user has to redefine the icons for their field type.
Proposals
Proposal 1
Add a
fieldIcons
export that maps the nodes to the field types. We should also use these internally to ensure consistency.The user can then use them alongside the FieldLabel API
Proposal 2
Add a
type
field to the<FieldLabel>
component. This may also provide an alternative path to resolving #528.The text was updated successfully, but these errors were encountered: