<?php

use App\Models\Bar1;
use App\Models\Bar2;
use App\Models\Bar3;

class Foo
{
    public function __construct(array|Bar1 $bar = null)
    {
    }
}

"Using type hints of "Union Types" or "Intersection Types" such as array|Bar1 or Bar1&Bar2 can cause the highlighting of the entire PHP file to malfunction."

Thank you for a great plugin!
It seems today's update has broken the integration for me. Now all imports are marked red as unused.
Is there anything I need to do on my local VS Code instance to get this working again, or is it a bug?

This extension uses the popular php-parser package to parse the code and highlight the unused classes. So far, the extension has support for 5/7, but not 8 yet.

I am opening this issue to keep track of this issue on php-parser and work on that once the release is made.

https://code.visualstudio.com/api/working-with-extensions/testing-extension#migrating-from-vscode

an example of this:

use function assert;

gets highlighted in red as unused but

use function \assert;

does not.

It highlights "use Trait" even if I'm using properties and methods of the trait.

Dear extension author,
Please publish this extension to the Open VSX marketplace.

Context

Unfortunately, as Microsoft prohibits usages of the Microsoft marketplace by any other products or redistribution of .vsix files from it, in order to use VS Code extensions in non-Microsoft products, we kindly ask that you take ownership of the VS Code extension namespace in Open VSX and publish this extension on Open VSX.

What is Open VSX? Why does it exist?

Open VSX is a vendor neutral alternative to the MS marketplace used by most other derivatives of VS Code like VSCodium, Gitpod, OpenVSCode, Theia-based IDEs, and so on.

You can read on about Open VSX at the Eclipse Foundation's Open VSX FAQ.

How can you publish to Open VSX?

The docs to publish an extension can be found here. This process is straightforward and shouldn't take too long. Essentially, you need an authentication token and to execute the ovsx publish command to publish your extension. There's also a doc explaining the whole process with an example GitHub Action workflow.

When using the word "use" in a variable it is marked as an unused use statement

I have been looking at a fix. Just need to get it tested, then I will submit a pr

If class is imported via alias, it will be highlight as unused.

because you only check regex from whole document content, your extension does not highlight when the usage is commented out.

When using PHP return types, this package things the use statement is unused.

<?php

namespace App;

// This gets highlighted incorrectly
use Example;

class Test
{
    public function foo() : Example
    {
         // ...
    }
}

Would be great to highlight unused imports after saving the file.
So you don't have to set a shortcut or trigger command all the time.

VS Code - Version 1.28.2 (1.28.2)

When I save, the file instantly highlights the unused class as expected, but when I then undo to add the class back, and save, the unused warning is still there until I click on another file and go back, or close the file an reopen it.

Thoughts?

sayHello should be renamed to php-import-checker ?

https://code.visualstudio.com/api/extension-guides/web-extensions

Any chance to implement group use declarations for php 7?

use Foo\Bar\{
    ClassA, 
    ClassB, 
    ClassC
};

VSCode Version: 1.28.0
Extension Version: 0.1.7

The red background highlighting seems too harsh. It's similar to what I see when errors are shown in my terminal.

In my opinion, a more friendly highlight color/option should be used.
Or let there be an option to set this in User Settings.

A similar extension for typescript, does this: