Add laravel extension

[haringsrob]

This pr adds Laravel tooling using the extractor in github.com/haringsrob/laravel-dev-tools

• Service container make
• Route autocomplete route('<>')
• View autocomplete view('<>')
• Model properties
• Model relations

[dantleech]

nice, feel free to concentrate on one feature at a time, that way we can ensure we're adding the necessary tests etc. plus we can merge quicker...

[haringsrob]

hey @dantleech I am about to pick this back up.

Regarding the external binary. It is for sure doable without I guess, but for me it would be more difficult at this point as I simply am not known enough to the phpactor codebase. Can keep using it for now?

Also, maybe I better split this work into a separate extension if that is still a possibility? Some thing I for sure need to do in the future is to have the ability to inject types into a file (see #1807)

Waiting for your advice.

[haringsrob]

Lot's of progress was made, may want to add some tests as well so I can avoid myself from breaking but also add failing tests for things I expect to work :), this however, would need a full laravel installation to work with, any suggestions?

[haringsrob]

• I refactored this out already so no need anymore I think.

[haringsrob]

It is in fact needed as I managed to use fully compiled blade for lsp resolving using a slightly modified compiler.

[dantleech]

i don't really feel comfortable depending on having a hard dependency on a framework component

[haringsrob]

Pretty sure i can copy just the needed parts over without all the rest

[dantleech]

impressive work so far 🎉 but please note that this branch should be treated as an experiment, it will be very difficult to review / merge this as it is, we should start creating PRs offering one feature at a time (or at least PRs that are of a small enough size). Any change to the Phpactor internals should be offered separately in individual PRs.

[haringsrob]

impressive work so far 🎉 but please note that this branch should be treated as an experiment, it will be very difficult to review / merge this as it is, we should start creating PRs offering one feature at a time (or at least PRs that are of a small enough size). Any change to the Phpactor internals should be offered separately in individual PRs.

Yes totally agree. It is however very hard to see of things work if I would have contributed smaller parts. I think one I have worked with it for a few weeks and things are stable I can start making pr's with tests of smaller chunks

[vivere-dally]

Hello! Sorry for bothering, but are there any updates on this issue?