Adam Lee

@alecritson yes you will see currently I have kept the global and auth components. Those could also be auto-loaded by setting overrideComponentAlias name is the component for backwards compatibility. ```php...

@alecritson Have you had chance to check this on your side yet I will mark it now for review. Would be good to get this merged over to develop next...

@glennjacobs might be worth holding back doing any more with the autoload as Livewire v3 will be released soon not sure if auto loading outside the app namespace is solved...

@glennjacobs Do you mind sharing what performance issues you came across?

I would say internally for the hub you certainly could introduce custom types. However when using the core models for the frontend we should not force the developer to use...

Ok makes sense as long as it gets merged to the new develop branch. I will create some further tests later if required.

I have already started to use this now for my client's project modifications. So I will continue my customisations and create some further tests so hopefully this can then be...

ok @alecritson What issues did you come across with this?

Ok however if every model was to bind to an interface. Then this would mean changing over the entire codebase to support this. With the way I have created this...

> When I was playing around with the testing, the biggest drawback seemed to be not being able to override existing methods, for example, the method `shouldBeSearchable` on the Scout...