Bug: NumberInput ids are created at build time and not at component initialization time about chakra-ui-vue HOT 4 CLOSED

Hey @peoray ! Sorry for my late response. I haven't looked at this thread since yesterday.

Just looked at the file. Yes, you're right. we can use the _inputId variable It can be fixed by removing the default property on the inputId prop. That's what's causing the id duplication.

from chakra-ui-vue.

Picking this up if it's still up.

So I'm a little bit confused.id generation is done by the useId function in utils. Either that or as a inputId prop passed by the user. What exactly do you mean by moving id generation to computed property?

@codebender828

from chakra-ui-vue.

Hey @peoray . Thanks for taking this up.

Currently there's an id prop that has a default.

The problem is that since this function is called at build time, and not at component instantiation time, this can result in the same value each time time the the component is used in the template.

To solve this we need to move that function call to the computer property. You can see this in the RadioGroup component.

from chakra-ui-vue.

Might probably sound silly but isn't the _inputId already a computed property or is there something I'm missing?

from chakra-ui-vue.