Formatting glitches with `unset()`

[SharakPL]

I use your extension as a formatter like this:

  "[php]": {
    "editor.tabSize": 4,
    "editor.formatOnSave": true,
    "files.insertFinalNewline": true,
    "editor.codeActionsOnSave": {
      "source.fixAll": "explicit"
    },
    "editor.defaultFormatter": "DEVSENSE.phptools-vscode"
  },

But it looks like it can't handle unset() properly.
It won't format this (other functions are formatted properly at this state):

Expected is this:

But when I format it myself and save, it reformats the code to this:

Does the extension implement all the psr-12 standards properly?
Can it handle project standards eg. .php-cs-fixer.dist.php in project root?

Would be much better if it showed specific rules that are not met by the code and will trigger formatting on save. Just like stylelint or eslint do it in VSCode's Problems tab, eg.:

[Miloslav]

Thank you for reporting this, it will be fixed.

Regarding the code style inspections, currently, we do not do that, but I'm taking a note to explore this in the future.

Thank you!

[Miloslav]

The fix will be present in the next pre-release. Thank you!

Regarding the PSR-12 question, it is fully supported; the issue you encountered was indeed a bug.

Please note that we do not read .php-cs-fixer.dist.php files, though. (yet)

[SharakPL]

Thanks 👍