Luke Towers
Luke Towers
Hmm, I think I have a better idea, let's just add in those assets dynamically in the layout file itself since that's where they're used anyways. Different layouts have different...
The point of this PR would be to pass those assets through the AssetMaker trait (instead of manually rendering them as script / style tags) so that their attributes can...
@bennothommo idea was along the lines of ```php $this->addAssets([...]) ``` in the layout files instead of directly rendering the asset tags; thus forcing them to go through the AssetMaker trait...
Yes, I'm fine with the ordering / prioritization changes staying. I don't think we'll have to do any extra passes on the layout because we can dynamically add them exactly...
This is desired behaviour, but yes, I believe I have an issue or something somewhere talking about different selection modes with folder being one of them.
Related: #19
@IsaiahPaget we use our own migration system entirely. Check the WinterUp command in the system module. I'm not opposed to either making our system more aligned with Laravel's implementation or...
@IsaiahPaget yes, there is. It would technically be a breaking change for anyone's workflow that makes use of `artisan migrate` without `--force` but with `APP_ENV` set to `production` but I'm...
@ericp-mrel are you able to add tests for this and a docs PR?
@ericp-mrel this might be useful to you: https://github.com/wintercms/winter/commit/d27dbbc5f8bb4b2df24c882b9d27dab521213294. There's two separate config keys, `cms.themesPath` and `cms.themesPathLocal`.