Jorge A. comments

Results 10 comments of


                                            Jorge A.

AutoComplete: Design tokens are not being used

You're absolutely right, @fatihsolhan. The issue appears when the multiple prop is enabled because the InputText becomes visible, and it brings its own design tokens. Here's what I've attempted so...

AutoComplete: Design tokens are not being used

@tugcekucukoglu I was waiting for any feedback before opening a PR, but I guess I'll just open it and wait for any feedback there before getting merged

AutoComplete: Design tokens are not being used

Hello @fatihsolhan. Don't worry about that! I’ve found a better solution to the issue. It would be appreciated if you could take a moment to review the PR and share...

fix(vue-form): losing reactivity

Would it be possible to watch default values key so it can update when it changes? This could be useful when fetching data, instead of creating a lot of computed...

fix(vue-form): losing reactivity

Hey @teleskop150750. Do you have any workaround until this is merged? I think it hasn't been reviewed yet since the main issue was closed

fix(vue-form): losing reactivity

Created the issue #1503 to track this PR 👍🏻

"Touched" definition in documentation is wrong

Thank you so much @BenGladman for the workaround. However, inputs already showing errors are validated again, but it works. @theVedanta Also thank you for your workaround! cc @crutchcorn

Defining `$fetch` within `useFetch()` doesnt pass cookies on SSR

Thank you so much @Aareksio. Your custom fetch worked! Hope the docs get updated for this use case.

After upgrading the Nuxt3 project to the latest version, an error occurred during the build (Nuxt 3.16.0 with Nitro 2.11.6 build)

Same error here! I had to downgrade to 3.15.4

Select: Design tokens with dt for the overlay are not working

Hey @asmussens. This also seems an issue to me. However, overriding the `overlay.background` token from the component layer in a custom preset solves this problem. So, as you said, the...