Having an Autocomplete with creatable and primitive options, if the options are empty and we wish to create a new one, the newly created option will not be a primitive but an object by default.
{"id": "x", "name": "x"} instead of 'x'
Expected behavior
The newly created option should be a primitive as expected in our case.
We might need a way to differentiate an Autocomplete with primitive options and one with object options.
Also, the "simpleValue" functionality seem redundant, we should only keep primitive functionality and remove "simpleValue".
Latest version
Current behavior
Having an Autocomplete with creatable and primitive options, if the options are empty and we wish to create a new one, the newly created option will not be a primitive but an object by default.
{"id": "x", "name": "x"}instead of'x'Expected behavior
The newly created option should be a primitive as expected in our case. We might need a way to differentiate an Autocomplete with primitive options and one with object options. Also, the "simpleValue" functionality seem redundant, we should only keep primitive functionality and remove "simpleValue".
see branch for failing test describing the issue https://github.com/osstotalsoft/rocket-ui-ts/tree/bug/creatable-autocomplete-primitive