load blade directives after resolving blade compiler

[tabacitu]

Tries to fix the issue reported in Laravel-Backpack/CRUD#4168 where the way we load blade directives stops OTHER packages from properly loading THEIR blade directives.

Inspiration for this PR came from:

• https://github.com/404labfr/laravel-impersonate/pull/25/files
• https://github.com/404labfr/laravel-impersonate/blob/master/src/ImpersonateServiceProvider.php#L72-L102

Note to self - it's possible that in packages that's the "proper" way to load Blade directives (not with Blade::directive() as you would do in a Laravel app). Otherwise if any package uses this method and is loaded AFTER our package, they won't have their directives loaded.

[tabacitu]

To use this branch, please do

composer require digitallyhappy/assets:"dev-load-blade-directives-after-resolving-blade-compiler as 2.0.99"
php artisan view:clear

[engel-m]

This PR fixed my issues with Laravel Impersonate and Spatie Permissions blade directives. All seems to be working fine.

[tabacitu]

Exceleeeent! Thank you @engel-m . I'll wait for @pxpm to also confirm, and merge this. In the meantime, you should be able to use this branch, no problem.

[pxpm]

I guess this is something related with the order of the providers or something, the directives work for me with or without this fix. (the spatie ones)

I did some search around too and came to the same conclusion as you, also found an issue on spatie/permission directly related to this spatie/laravel-permission#278

I think the PR is clean, and it works indeed, I was just wondering if developer added some custom Blade::directive in their provider it would break ours. I tested and it does not break, I can't be happy with this and installed the impersonate package to see what was happening.

It happens that without this branch impersonate does not work, but spatie keeps working. With this branch both work ... so yeah. I will leave it here.

[tabacitu]

Awesome! Merged & tagged 🎉
This was a weird one...