Option to assign links to files path

[kanlukasz]

I would like to ask if you have any plans to add a function that will create links in php files.
I mean something like this:

There are several extensions with these features, but they don't always work the best:

• https://marketplace.visualstudio.com/items?itemName=pwarchol.vscode-php-file-link
• https://marketplace.visualstudio.com/items?itemName=jack89ita.open-file-from-path

It would be great to have such a native tool in your PHP Tools.
What do you think?

[jakubmisek]

Thank you for the suggestion!

Yes, we need to add file names code completion and links for file names as well.

Working on it.

[jakubmisek]

The feature is available in the latest pre-release (1.38.13932), thank you for the suggestion!

[kanlukasz]

Thank you so much for taking care of it so quickly.
I've done some tests:

1. Some links are inactive, eg.:
   

2. Links lead to wrong files (it seems that file search works with wildcard?)
   

3. The link looks like a split <name> . <extension>. Or is it a matter of settings in VsCode?
   

4. If I may make a suggestion, it would be much more readable for duplicate files if it worked this way:
   

we need to add file names code completion

Does this also work anymore?
I tried typing the file name in require_once and there is no suggestion/completion

[jakubmisek]

@kanlukasz you're right, currently, we resolve the paths only after __DIR__, __FILE__ and dirname(). But it's a good idea to understand more "dynamic" contexts, like this one in WordPress.

[jakubmisek]

@kanlukasz
3. and 4. are provided by VSCode itself.

But we'll handle more cases in WordPress more precisely, so it will be resolved exactly.

[kanlukasz]

@jakubmisek

1. Ok thanks

2. Is there a plan to fix this?

3. Ok thanks

4. What does VSCode provide here? I just suggested a different way of implementation here :) I mean, the add-ons I mentioned at the beginning of the thread solve the problem of duplicates in this way

[jakubmisek]

First, VSCode asks extensions (like ours) if it knows exactly.

Then it simply looks up all the files matching the name in your workspace.

2/ We need to handle WPINC (and other constants) to handle the file path better. Working on it. Currently we understand file paths after __DIR__, include, dirname(...)