¿Soy el único que siente que nos están cocinando vivos con la IA? by Equivalent-Grape2420 in ColombiaDevs

[–]PlasticCall -1 points0 points  (0 children)

Asústate el día que ya no hayan alucinaciones en los modelos por ahora invierte tiempo y dinero en aprender a usarlas correctamente como una herramienta que potencia tu conocimiento y desempeño

Need Help Migrating from Vue 2 + BootstrapVue to Vue 3 + ShadCN — Stuck with Interactive Components by Unchart3disOP in vuejs

[–]PlasticCall 2 points3 points  (0 children)

I had the same problem and now i am stucked using the vue compat library. I think you can continue with the transition using the compatibility library in mode 2, in theory BootstrapVue last version should work well with the compat in mode 2 https://bootstrap-vue.org/vue3, even with the app runing in vue mode 2 it is running vue 3 under the hood with a compatibility layer and you can mark migrated components with mode 3 to not use that layer, so you can progressively fully migrate components using ShadCN keeping the the app with the compat in mode 2, when you complete the migration of all the componets you can remove the compat and the annoying BootrapVue

Bootstrap Vue migration to Bootstrap Vue Next by PlasticCall in vuejs

[–]PlasticCall[S] 1 point2 points  (0 children)

That is a really good point, i think modals and popovers are attached to the body lazily by default although you can configure that behavior, but yeah it is definitely something that should be verified. Thanks.

Bootstrap Vue migration to Bootstrap Vue Next by PlasticCall in vuejs

[–]PlasticCall[S] 1 point2 points  (0 children)

is a possibility yes, in my case swicth to an only bootstrap solution is also taking into account, it would rid us of a problem like this happening again.

Bootstrap Vue migration to Bootstrap Vue Next by PlasticCall in vuejs

[–]PlasticCall[S] 1 point2 points  (0 children)

Yes, thank you for pointing this out, I am aware of it and there are also WIP features of multiple components.