christo9090
christo9090
Just wanted to jump in here and say I am having the same problem. I have a button which changes the keys to display a different set of data and...
@plouc Yes unfortunately I am on version 0.74.0 for `@nivo/bar` and `@nivo/core`. I see the updates to react-spring in the dependencies as well. Every time I change the key for...
2nd this issue. Just ran into it. No way to access the input via the ClassNames prop.
Agreed. Just upgraded from next ui 2.2.1 -> 2.2.9 and now none of the inputs where I was using register() from React Hook Form populate the default values. Contoller inputs...
For debugging purposes, register from react hook form adds the following props to the input: ``` { name: 'title', onChange: ƒ, onBlur: ƒ, ref: ƒ } ```
> Same issue, `defaultValues` does not work. Now need to manually pass `defaultValue`. Just a guess then. but if the register() function never returned a default value, I am guessing...
> wrapping the NextUI Input with a Controller fixes the default value problem > Did you try using this way This does fix it but it sort of defeats the...
> when trying to pass `{...register("field")}` I have seen all of these same issues. I dug into this a ton before giving up and just wrapping every Input in my...
@cvolant Can you tell us more about your solution? This one really bugs me too. It seems very easy to get the ref from the `register()` applied properly.
> > And worst of all, the title doesnt change on page navigation even though each route has a head.tsx with the being exported as a react fragment > >...