Typos/misspellings masked by plugin

[FrankDomina]

Is there a reason that enabling this plugin appears to disable all spelling checks? This makes it difficult to find using mistyped variable names.

I realize that using an initialized variable is technically okay in PowerShell, but one way of catching unintentional uses of that, um, "feature", is to see IntelliJ report misspellings for variables. For example:

$myVariable = someFunction -Param $someParam

if ($myVarable) {
    # do something
}

With spell-check, it would be obvious that the "if" contains a typo. Without spell-check, which this plugin apparently disables, and without this plugin reporting the use of uninitialized variables, errors go unnoticed. (Relying on spell-check is not perfect, but it's better than nothing.)

And that's not to mention that without spell-check, strings could have misspellings, too. Not cool!

Ideally, it would be awesome if this plugin could actually be configured to report the use of uninitialized variables, but unless that is implemented, it would sure be nice if spell-check functioned without having to disable this plugin.

[ForNeVeR]

There's no reason for this and it is not expected. It could be that we do something unsupported with the PSI (the way IntelliJ calls its internal AST), or do not inherit from some required classes for our PSI structure to be considered "textual" (and thus pass the spellcheck). We'll need to fix this.