Required enum field still renders an empty option

[fourteenmeister]

Prerequisites

• I have searched the existing issues
• I understand that providing a SSCCE example is tremendously useful to the maintainers.
• I have read the documentation
• Ideally, I'm providing a sample JSFiddle, Codesandbox.io or preferably a shared playground link demonstrating the issue.

What theme are you using?

core

Version

6.4.1

Current Behavior

Bug

I understand that showing an empty option for enum/select fields may be intentional in the general case, and the docs describe empty-value behavior for selects. But for a required enum field this looks incorrect, because the schema does not allow an empty value and the UI still shows a blank selectable item.

Actual

An empty first option is rendered even though the field is required and the enum contains only non-empty values.

Expected Behavior

A required enum field should not render an empty option unless that empty option is explicitly defined by schema or uiSchema.

Steps To Reproduce

Sandbox reproduction

[nickgros]

@fourteenmeister Are you able to add one of the values as a default in the schema (example)? That is the logic we currently use to remove the empty option.

[fourteenmeister]

@fourteenmeister Are you able to add one of the values as a default in the schema (example)? That is the logic we currently use to remove the empty option.

Yes, default does indeed solve the issue with rendering an empty option in the select.

However, explicitly setting a default still feels a bit odd in this case, since the user is required to provide a value anyway (because the field is marked as required).

[x0k]

This may lead to a situation where a required field inside an optional object cannot be cleared (#4954). It seems that this behavior should be configurable via the UI schema.

[fourteenmeister]

This may lead to a situation where a required field inside an optional object cannot be cleared (#4954). It seems that this behavior should be configurable via the UI schema.

you mean this case? example

[x0k]

Yes, but that feature (removeEmptyOptionalObjects) hasn't been released yet, so you can refer to this example

[fourteenmeister]

ok, thanks - clearable flag solve this problem.
waiting for release this feature)

[x0k]

@fourteenmeister , I meant that the removeEmptyOptionalObjects feature is not yet available in the RJSF playground, so I created a demo based on my own project.

Regarding the clearable feature, its implementation in RJSF depends on the project maintainers, so please keep the issue open and wait for a response. You can also indicate whether you would like to work on implementing this feature.

[fourteenmeister]

@fourteenmeister , I meant that the removeEmptyOptionalObjects feature is not yet available in the RJSF playground, so I created a demo based on my own project.

Regarding the clearable feature, its implementation in RJSF depends on the project maintainers, so please keep the issue open and wait for a response. You can also indicate whether you would like to work on implementing this feature.

ok! Reopened this issue