> Hi. I think this patch was from some months ago and we had a conversation some other way (IRC? Fediverse?) where you explained that the functionality was already there.


I remember that! And that’s really interesting because I received the patch
last night :)

Glad to hear it’s not an issue anymore at least!

-Kristófer R.

Hi Garret, thank you for the patch!

This functionality should already be available by typing in either a
path to a phpcs rule file (such as `phpcs.xml` or
`../other-project/phpcs.xml`) or by typing in the name of the standard
installed alongside phpcs, e.g. via composer (such as `WordPress-Core`).
You type this into the same box that provides the pre-filled standards.

As an example, the projects I work on have a `phpcs.xml.dist` file in
the root of the repositories and I can just manually type in
`phpcs.xml.dist` in the UI to have phpcs use those rules.

Maybe this isn't clear from the UI? I thought I put in a better
description for the option, but that clearly isn't the case.

Hi Christian,

> Hi, any updates on this since Nova 10 has been released?

Not yet. I’ll work on this when I have the time, unfortunately that’s not right
now. I also don’t know exactly when I’ll have the time. Depending on how the
holiday season goes it may not be until next year.

I’m happy to review and merge patches that implement this, but even that will
likely take a couple of weeks since my schedule is pretty packed until the New
Year.

-Kristófer R.

After you update the extension to version 1.2.2 and enable the debug option
there should be 2 Intelephense sources in the list of extension sources there.
I think you copied the one from "Intelephense Language Server", could you send
me the output from the one called "Intelephense"?

If it’s not there you need to update the extension, enable the debug setting in
the extension preferences, and restart Intelephense.

-Kristófer R.

Hi!

> Intelephense Language Server[11:05:08.791000] env: node: No such file or directory

This implies Nova can’t find your installation of NodeJS when running the
extension. If you open your terminal application and run `which node` what is
the output? If it’s in a non-standard location (i.e. outside /usr/bin or a
variation thereof) you may have to make sure it’s added to your PATH in Nova.

Usually the easiest way to accomplish this is to ensure Nova is using the
environment from your login shell. You can toggle this in the Nova preferences
and in the "Tools" section. You can also manually modify some of the environment
variables there.

The problem has been fixed in Nova 10 and the Psalm extension now works as
intended.

-Kristófer R.

Following up on this, this has been confirmed to be an issue in Nova [0]. The 
Nova devs are planning on fixing this when Nova 10 is released, so we’ll just
have to wait for the next release.

[0] https://devforum.nova.app/t/lsp-stops-because-of-an-error-i-dont-understand/1749/3

-Kristófer R.

Hi all, sorry for taking so long to respond.

I’ve looked into this as well and can’t find any reason for why this error
should be popping up. I’ve asked the Nova devs to check things out. I suspect
this may be a regression since I haven’t changed anything between the time the
extension was working and now that it’s not.

Hopefully they’ll get back to me soon so I can update the extension such that
it works again.

-Kristófer R.

Hi again Joshua,

Format on save has been implemented and released in version 1.4.0.

-Kristófer R.

Sure, I’m working on this now. I have a rudimentary version of this ready but
want to test it more and clean up the code before I release support for this.

-Kristófer R.