[Feature Request]: dynamic view path

[kminek]

Feature Description

hi,

this works as expected (i am getting IDE autocompletion for $posts variable inside blade template):

view('controllers.post.index', ['posts' => $posts]);

however this doesnt:

$v = 'controllers.post.index';
view($v, ['posts' => $posts]);

is there some kind of custom dockblock to help Laravel Idea to undestand this and provide autocompletion for $posts variable in blade?

[gorbunov]

Laravel Idea doesn't run php, so runtime evaluation of values inside variables is impossible.

But if your blade template relies on variables of known type, you can just hint them inside template, even without plugin:

Maybe this will help in your case?

[kminek]

yes i am aware you can type hint variables directly at the top of blade template. i was just wondering if i can avoid that - when the number of variables grows its quite tedious process to update those :) anyways thanks for quick reply and help 👍

[gorbunov]

yes i am aware you can type hint variables directly at the top of blade template. i was just wondering if i can avoid that - when the number of variables grows its quite tedious process to update those :) anyways thanks for quick reply and help 👍

We will iterate a little internally on this, technically we can read some custom phpdoc before / inside view() call, but generally we try to avoid adding something into code that specific to our plugin.

[adelf]

$v = 'controllers.post.index';
view($v, ['posts' => $posts]);

We can make it work, but I think your case is more complicated. Could you share any real samples?

[kminek]

$v = 'controllers.post.index';
view($v, ['posts' => $posts]);
We can make it work, but I think your case is more complicated. Could you share any real samples?

basically i have custom function default_view(['posts' => $posts]) that constructs view path dynamically following some convention. so if i put it inside PostController::show method the constructed path will be controllers.post.show etc. i think some custom phpdoc to tell Laravel Idea where the view actually is would be helpful in my case. but of course there may be other cases where view path is constructed dynamically in real codebases.