Dropdown's useOptionAsValue does not take precedence

[dingzhanjun]

Describe the bug

I use dropdown to display a list of data, in the onChange event, the event.value is always property's ID instead of whole option object when useOptionAsValue presents

Reproducer

https://stackblitz.com/edit/vitejs-vite-rrgaoc?file=src%2FApp.tsx

System Information

React: 18.2
Primereact: latest

Steps to reproduce the behavior

select one item from dropdown, it display option's ID when both useOptionAsValue and optionValue present

Expected behavior

when both useOptionAsValue and optionValue present, useOptionAsValue should take precedence and select value should be the whole option object

[melloware]

@Rekl0w related to #7134

[Rekl0w]

This will work, you shouldn't use optionValue prop if you want to get the whole object. If you have an object that has value key but you don't want to pick the value key, then you should use the useOptionAsValue prop, yet it works both ways. I changed the PrimeReact version from latest to 10.8.3 at Stackblitz link.

[dingzhanjun]

Is the latest not the same with 10.8.3?

[melloware]

what we have seen on StackBlitz is latest is sometimes cached and changing it to 10.8.3 or whatever version forces it to reload.

[Rekl0w]

Agreed. @melloware

[dingzhanjun]

Thanks for your quick response, there is something I do not understand, here is the code from dropdown

const getOptionValue = (option) => {
            if (props.useOptionAsValue) {
                return option;
            }

            const optionValue = props.optionValue ? ObjectUtils.resolveFieldData(option, props.optionValue) : option ? option['value'] : ObjectUtils.resolveFieldData(option, 'value');

            return props.optionValue || ObjectUtils.isNotEmpty(optionValue) ? optionValue : option;
        };

the code shows that useOptionAsValue should always take precedence

[Rekl0w]

It is already. You can try it with or without useOptionAsValue prop at my provided Stackblitz link.

[dingzhanjun]

your does work, I was wondering why, it does not make sense according to the code

[Rekl0w]

Which code are you talking about ? Stackblitz link or codebase ?

[dingzhanjun]

the code snippet posted above from code base, props.useOptionAsValue should take precedence:

const getOptionValue = (option) => {
            if (props.useOptionAsValue) {
                return option;
            }

            const optionValue = props.optionValue ? ObjectUtils.resolveFieldData(option, props.optionValue) : option ? option['value'] : ObjectUtils.resolveFieldData(option, 'value');

            return props.optionValue || ObjectUtils.isNotEmpty(optionValue) ? optionValue : option;
        };

[Rekl0w]

Like i said it already has precedence. It is placed top of the function and has return.

[dingzhanjun]

Sorry, I misunderstood, could my stackbliz be because of cache that does not load the latest package

[Rekl0w]

It can be.

[dingzhanjun]

thank you so much!

[Rekl0w]

You're welcome.