joffreypersia wrote a comment+100 XP
3mos ago
@Crisis2k Thank you. Good news for me, I think it is simpler, so better.
joffreypersia liked a comment+100 XP
3mos ago
In case anyone watches this and gets confused — Claude have announced that Commands have been merged with Skills in version 2.1.3. https://code.claude.com/docs/en/changelog#213
joffreypersia started a new conversation+100 XP
3mos ago
joffreypersia wrote a reply+100 XP
5mos ago
I am using ShadCN-vue https://www.shadcn-vue.com/docs/components/checkbox But it doesn't talk about v-model
Under the hood, it is reka-ui : https://reka-ui.com/docs/components/checkbox
joffreypersia liked a comment+100 XP
5mos ago
When I'm using VueJS, I create my own checkboxes, radio buttons, ... and generally I hide the native input element and show my custom one.
To display the validation errors, it depends if the errors come from the backend (just retrieve the errors) or if you also validate frontend side (you can use vuelidate).
joffreypersia wrote a reply+100 XP
5mos ago
joffreypersia wrote a reply+100 XP
5mos ago
joffreypersia started a new conversation+100 XP
5mos ago
Hi,
I'm working on a Laravel + Vue.js + Inertia v2 project and struggling to find the right approach for form handling with non-native form elements.
My setup:
- Using Inertia v2's new <Form> component (https://inertiajs.com/docs/v2/the-basics/forms)
- Using shadcn-vue components for UI (https://www.shadcn-vue.com)
The problem: Shadcn-vue components like Checkbox don't render native HTML inputs underneath, so Inertia's <Form> component doesn't detect changes for dirty state tracking. The checkboxes work, but the form never becomes "dirty" when I toggle them.
What I've tried:
- Adding hidden native checkboxes alongside shadcn checkboxes (complex and messy)
- Using v-model on hidden inputs (doesn't work with <Form> component)
My questions:
- Should I use the <Form> component or fall back to useForm() for better reactivity with shadcn components?
- Do I need to wrap shadcn components in a custom Field component to bridge them with Inertia?
- What's the recommended pattern for using non-native form components with Inertia v2?
I need basic features: dirty state detection, validation errors display, and proper form reactivity.
How do you handle this in your projects?
Thanks, Joffrey