Fix dynamic components

[bakerkretzmar]

Fixes <x-dynamic-component> Blade components, which don't work but should have been supported (and might have worked at some point in the past).

All this does is override the DynamicComponent component class so that it uses Jigsaw's customized ComponentTagCompiler instead of Laravel's. I didn't even change anything in DynamicComponent, just the fact that we redeclare it picks up the new compiler because of the namespace it's in.

There might be more nuance to explore here, this is super basic and just makes the happy path example in the included snapshot test work as expected.

Closes #707.

[bakerkretzmar]

Leaving the formatting action broken here because it changes a ton of files. I'll fix it separately.

[stevenmaguire]

@bakerkretzmar thanks for getting this going. I think this is the most prudent strategy.

There might be more nuance to explore here, this is super basic and just makes the happy path example in the included snapshot test work as expected.

The basics working is a good sign. If you're looking for most use cases, my specific use case is that I am using "class backed" components in the \Components jigsaw project namespace. I know that there is a logical fork in the component detection logic - one to source the path of the php class that backs the component and one to source the path of the blade template if the first fails. Perhaps ensuring that use case is handled in your solution would help build confidence?

[damiani]

Fantastic, thanks @bakerkretzmar !!

[stevenmaguire]

Thank you both!