Optional string enumValue?

[rickpasetto]

First, let me say this is an awesome framework. Thanks to everyone who has contributed!
I'm still fairly new to this library, so I'm still learning how to use it. I'm trying to do something I think is fairly simple: add a field to a collection that you can select from an enum, just like the example in the docs, e.g.:

const colors = { RED: "red", GREEN: "green", BLUE: "blue" } ... { name: "Color", dataType: "string", validation: { required: false }, enumValues: colors } 

However, notice that I want this to be an optional field, so can be removed from the Firebase object. I want the user to be able to "un-set" the field in the UI. When I run this, the field initially shows as blank, but after it is set, there's no way to "delete" the field value.

Is there a way to do this?

Any help would be greatly appreciated.

[fgatti675]

Hi @rickpasetto
This is not possible at the moment.
As crazy as this sounds, this issue has not been raised in the 2 years life of the project 😂
Feel free to create a new issue! It should be fairly straightforward to implement

[fgatti675]

It is possible now with the clearable prop in some properties

[fgatti675]

It is possible now with the clearable prop in some properties

[serhii-sierov]

Used clearable: true. Got a dropdown with a “Clear” icon. But when clicking “Clear”, it doesn’t clear the value — it just opens the dropdown.
(Relevant for string properties where enumValues are set)

[fgatti675]

Thanks for reporting! Looking into it now

…

On Sat, Jun 21, 2025 at 1:08 PM Serhii Sierov ***@***.***> wrote: Used clearable: true. Got a dropdown with a “Clear” icon. But when clicking “Clear”, it doesn’t clear the value — it just opens the dropdown. (Relevant for string properties where enumValues are set) — Reply to this email directly, view it on GitHub <#390 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABHCCD5ASRQMJFSP5Q7E2UL3EU4KLAVCNFSM6AAAAAB72ADUGWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGNJTG4ZDENI> . You are receiving this because you commented.Message ID: ***@***.***>

[serhii-sierov]

It seems it is a known issue: #391