Feature/add attributes to blade directives

[juliomotol]

This PR aims to improve the current blade directives available with the following notable changes:

• Can now pass multiple parameters to the @mixSri and @assetSri blade directives.
  • Before, @mixSri('app.css', true) doesn't work since the directive because when extending the directive, it only allows 1 parameter.
• A third parameter has been added to support other attributes for script and link tags attributes.
  • The new signature is @assetSri(string $path, bool $useCredentials, string $attributes).
• The blade directive logic has been moved to the Sri class.
  • Did this to allow multiple variables to pass through in the blade directives.

This PR also adds tests for the blade directives which there wasn't any before.

[juliomotol]

I just saw PR https://github.com/Elhebert/laravel-sri/pull/37 and I think this is a cleaner solution since $attributes is more general than $execute but the idea is pretty much the same.

[Elhebert]

Nice PR, I'll have a deeper look later this week.

I think that I might remove the Blade directive soon to use Blade component that will provide a far better DX 🤔

[juliomotol]

Interesting! On v3 maybe?

I also noticed that you're setting an alias for Sri::class with sri in lowercase. Normally, aliases are pointed to the facade and is CamelCased.

https://github.com/Elhebert/laravel-sri/blob/6df0ce2b5f9f19f08b9bbd40e9b1015cbef842ca/src/SriServiceProvider.php#L18

$this->app->alias(SriFacade::class, 'Sri');

[Elhebert]

I think I will first do a new minor with the components, then remove them in a major version (so yeah 3.0). It's a bit hard for me to work on this package as I'm currently not working with Laravel anymore. But I do intent to do a full rewrite for a v3 at some point.

For the Alias I think we can remove the one in the service provider because I set one in the composer.json:

https://github.com/Elhebert/laravel-sri/blob/master/composer.json#L42-L44

[juliomotol]

I see. I also have a few concerns that could be implemented in v3 if you are open for an RFC.

[Elhebert]

I'll create an issue for v3 improvements.

See #57.