Why doesn't packaging auto include partials and macropartials?
Just curious why the default behavior for creating a package would be to not include partials and macropartials, they seem every bit as important as views. Is it an oversight or intentional? Or am I doing something wrong?
That is just the way it works right now - you need to add the files/folders explicitly. I think that's a good thing since it allows you to cherry pick exactly the files and items that you need for your package.
Creating a package can be used for deployment or quick "copying" of parts of functionality to be used on other websites or for creating a package other can use and install as well. So auto including stuff is always ideal in every scenario in my humble opinion.
Why doesn't packaging auto include partials and macropartials?
Just curious why the default behavior for creating a package would be to not include partials and macropartials, they seem every bit as important as views. Is it an oversight or intentional? Or am I doing something wrong?
Hi Matthew
That is just the way it works right now - you need to add the files/folders explicitly. I think that's a good thing since it allows you to cherry pick exactly the files and items that you need for your package.
Creating a package can be used for deployment or quick "copying" of parts of functionality to be used on other websites or for creating a package other can use and install as well. So auto including stuff is always ideal in every scenario in my humble opinion.
/Jan
Sounds reasonable, thanks much for clarifying things.
Always at service ;-)
/Jan
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.