Typehinting in blade components

[edwinvdpol]

All Submissions:

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?

New Feature Submissions:

1. Does your submission pass tests and did you add any new tests needed for your feature?
2. Did you update all templates (if applicable)?
3. Did you add the relevant documentation (if applicable)?
4. Did you test locally to make sure your feature works as intended?

Changes to Core Features:

• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your core changes, as applicable?
• Have you successfully ran tests with your changes locally?

This will improve IDE autocompletion in blade files where applicable.

I would like to cleanup / structurize the blade files even more after this PR to make things more readable and consistent.

[lrljoe]

Wow, lot of changes here! It'll probably be the weekend before I can review this properly.

Really appreciate the contribution!

[lrljoe]

Mostly reviewed & all okay so far, couple of files left for later this weekend, just the larger files that I need to skim over

[lrljoe]

Just the big one (datatable.blade.php) to go, I'll look at that tomorrow, and get this merged in.

[lrljoe]

@edwinvdpol - while testing across different versions of PHP & Laravel, it seems that some supported versions presently misbehave with the typehinting in place:

This behaviour goes aware without the typehinting.

For the time-being, I'll be rolling back the typehinting in the blades

[edwinvdpol]

Not sure what you mean, but allright. 😉
Can you specify which version of PHP and Laravel, and what goes wrong?

[lrljoe]

Threw a screenshot on the last update, need to go through and validate the different environments it happens in to know for sure where it's coming from.

Effectively it's turning a chunk of the toolbar into HTML rather than blade (see screenshot)

Unsure if it's a cdn issue/specific config issue. at the mo, but backing it out resolved it.

Just need to ensure it doesn't break anyone's existing deployments.

I am definitely keen to get it added in tho