Per-file shell override?

I have a file that works in multiple shells, and is sourced not executed, so I don’t want to put a shebang directive in it (also, a “shell” directive would imply it only works on one shell, and I’m not aware of how i can tell shellcheck i want to check multiple shells). I usually lint it on the command line with shellcheck -s sh path/to/file && shellcheck -s dash path/to/file && shellcheck -s bash path/to/file etc.

It would be great if:

1. i could provide a filename in the extension settings, and override the shell (ie, the -s value) for it
2. i could provide multiples and have the extension warn me about the union of all the warnings

[felipecrs]

My concern is about the cleanability of the code. I have the impression that such a new feature would not be simple and could add a burden in terms of maintainability (and we lack maintainers).

But I would be happy to be wrong and review any PRs. 😉

Therefore, I will keep it open for a while.

[ljharb]

I totally agree that would be ideal, but given that that one’s 6 years old, it doesn’t seem likely to be implemented - in which case it’d be pretty helpful to have it here.