Add emptyOptionValue configuration option

[malon43]

This change allows for an empty option that does not necessarily have a value="", but any specified string.

[oyejorge]

I'm not sure how this would change how Tom Select works, values other than "" (empty string) are already handled normally

…

On Tue, Nov 21, 2023, 06:09 malon43 ***@***.***> wrote: This change allows for an empty option that does not necessarily have a value="", but any specified string. ------------------------------ You can view, comment on, or merge this pull request online at: #661 Commit Summary - c01e3d0 <c01e3d0> Add emptyOptionValue configuration option File Changes (6 files <https://github.com/orchidjs/tom-select/pull/661/files>) - *M* doc_src/pages/docs/index.md <https://github.com/orchidjs/tom-select/pull/661/files#diff-45fb238e0097b83c281088006299490d9b8d8e0f8e9b95598c71921e476dc7fb> (8) - *M* src/defaults.ts <https://github.com/orchidjs/tom-select/pull/661/files#diff-89980272e809330d127c328f417c6e7d94ba3c2fd402357f78eff49671c88f09> (1) - *M* src/getSettings.ts <https://github.com/orchidjs/tom-select/pull/661/files#diff-f22b9c75993acbfddb0fb9b995cbaf846d1eab2e55f487f5798519a6facdbf18> (8) - *M* src/tom-select.ts <https://github.com/orchidjs/tom-select/pull/661/files#diff-a5b86ab78740a77920c9adb8e6fbccfab70018b535d22a39d2f2b91d5bd1c21a> (3) - *M* src/types/settings.ts <https://github.com/orchidjs/tom-select/pull/661/files#diff-164e15b52eb58666ab9850117737ff314ee3e1a835a99f7f34a3e0f232c22589> (1) - *M* src/utils.ts <https://github.com/orchidjs/tom-select/pull/661/files#diff-39b2554fd18da165b59a6351b1aafff3714e2a80c1435f2de9706355b4d32351> (5) Patch Links: - https://github.com/orchidjs/tom-select/pull/661.patch - https://github.com/orchidjs/tom-select/pull/661.diff — Reply to this email directly, view it on GitHub <#661>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAH6YRBYBA4YF3F5UCD6LWDYFSRXDAVCNFSM6AAAAAA7URN5MSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGAYDIMRVGIYTINA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[malon43]

Sorry for not being clear. Yes, the problem is that the values are always handled normally, even when the desired "Empty option" would have a different value from "".

E.g. QuerySelectField from wtforms - SQLalchemy when passing allow_blank=True, will add an empty option, with value="__None", and right now there is no way to directly handle this in tom-select if the desired outcome is not showing the empty option and sending "__None" in the case the user does not pick anything.

[malon43]

@oyejorge are there any plans of having this request merged?