Tabs Component not working "out of the box" #31
-
|
Hi! I was trying your starter kit and encountered this situation while installing new components (tabs). It is my understanding that the starter kit comes with pre-installed components that are located at "resources/views/components/ui". Now, when I install a new component, it goes to a different location "resources/views/ui". Is this intended as default? My understanding from the documentation is that i just have to install the component using artisan and that's it. By just adding the tag "x-ui" I should be able to play with the new components. In my case, that is not happening. I manually moved the component into the "view/components/ui" folder and i could partially see the component but not completely. Anybody else having this same issue? (my knowledge in the Laravel architecture is not well develop to figure this one on my own.) |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
Hii, you're right, it's my mistake. I configured the tabs component under views/ui instead of components/ui. the issue now has been fixed thank you! |
Beta Was this translation helpful? Give feedback.
-
|
the issue of the tabs rendered partially (mostly only the triggers that render tabs and not panels) is because the code you copied from the docs is broken. Now it's fixed, I think you can use the tabs without issues. |
Beta Was this translation helpful? Give feedback.
the issue of the tabs rendered partially (mostly only the triggers that render tabs and not panels) is because the code you copied from the docs is broken. Now it's fixed, I think you can use the tabs without issues.