You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the install and craftable-pro:generate-crud artisan commands, it generates the front-end files in the /resources/js/craftable-pro directory. In the application I'm working, that is a problem because I don't have a js folder; my pages and components folder are directly in the /resouces/ folder.
Since I also use Inertia.js with vue for my application front-end, I already have a configuration for the @ alias, which is just /resources, but the front-end files generated by craftable-pro expects it to be /resouces/js.
My work-around for the moment is to move all files from /resources/js/craftable-pro to resources/craftable-pro after they are generated, but I think that making this a config option would be a great solution!
Thank you!
The text was updated successfully, but these errors were encountered:
Hello there!
When using the install and
craftable-pro:generate-crud
artisan commands, it generates the front-end files in the/resources/js/craftable-pro
directory. In the application I'm working, that is a problem because I don't have ajs
folder; my pages and components folder are directly in the/resouces/
folder.Since I also use Inertia.js with vue for my application front-end, I already have a configuration for the
@
alias, which is just/resources
, but the front-end files generated by craftable-pro expects it to be/resouces/js
.My work-around for the moment is to move all files from
/resources/js/craftable-pro
toresources/craftable-pro
after they are generated, but I think that making this a config option would be a great solution!Thank you!
The text was updated successfully, but these errors were encountered: