@N1ebieski thanks for reporting this - this totally makes sense.

What linter or setup are you using that causes it to send a number or an object?
I'd like to try to reproduce the issue.

Hi @TitasGailius, I'm using WSL Linux with Docker and working with the extension in dev container mode. For me, it's only an object, not a number.

@N1ebieski There must be another extension, a special rule in .vscode/tasks.json, or something else providing diagnostics for environment variables.

An easy way to check where this is coming from is by inspecting the diagnostic.source value.
If it's coming from the extension, it should be Laravel Extension.

The reason I'm asking is that it doesn't seem to be provided by the Laravel Extension itself, and I'd like to understand the actual source.

@TitasGailius

@N1ebieski interesting. Thanks for checking.

@N1ebieski, your version of the extension includes these changes:

https://github.com/laravel/vs-code-extension/pull/443/changes#diff-cba9592099e8717965c26e4a4fbf5f49ec33850cb90f8750e555ed4ddf35cd15R94-R97

The main branch does not have them yet, so code is always a string.

@TitasGailius You're right. On the main branch I have a string, but when working on N1ebieski:Improvements-for-linked-parameter-vscodeDiagnosticcode-for-diagnosticProvider-#55, I get an object.

@TitasGailius OK this is why > https://github.com/laravel/vs-code-extension/pull/443/files#diff-cba9592099e8717965c26e4a4fbf5f49ec33850cb90f8750e555ed4ddf35cd15R94-R97

Please let me know whether I should remove these links and keep only the Quick Fix option:

If so, this PR can be closed.