Hi again Christian,

I've just published version 1.3.0 of Intelephense with support for 
adding a license key and using the premium features Nova supports. As 
far as I've been able to tell that's really just the "Jump to 
implementations" feature for now, but maybe there are other things I 
just don't know how to find in Nova's UI.

-- 

Best regards,
Kristófer R.

Hi Martin,

> it would be great if the Intelephense Nova extension would have a per project setting for enabling’/disabling the extension.

I've just added this in version 1.3.0 of the extension released tonight :)

-- 
Best regards,
Kristófer R.

Hi, I've just added this to the upcoming version 1.3.0 that will be 
released later tonight. All the diagnostics options should be available 
with that version.

Hope that helps!

-- 

Best regards,
Kristófer R.

Hi! Thank you for bringing this to my attention, and sorry for the late 
reply!

> It looks like I would need to set intelephense.diagnostics.undefinedProperties = true, but I don’t know how to do that with this extension.

This wasn't an option before. Intelephense has a lot of configurable 
options and I didn't add them all because it takes a lot of time. I've 
already implemented this and it will become available in the upcoming 
1.3.0 version of the plugin that should be published later today.

Let me know if you're still running into this problem next week!

-- 
Best regards,

Hi Graceson,

Sorry for taking so long to reply, I've had a busy couple of months.

The extension works for me, and the logs you list in your email seem 
fine to me, they're the same I see in projects I work on that use Psalm 
and the extension works fine.

 > I am running PHP 8.2.7, Nova 11.2 trial, and Psalm 
dev-master@2e8d575543c73bae8f9fd3ac46957699c0b90903.

I'm using PHP 7.4.33, Nova 11.3 build 534827, and Psalm 4.13.1. Not sure 
how outdated my Psalm version is, but that might be part of the problem. 
Seems a bit unlikely though since the output from the extension console

Hi Steven!

Thanks for the detailed reproduction steps! I’ll try to take a look at this
later this week and apply the fix suggested by Logan.

-Kristófer R.

Hi Steven!

> I'm noticing that if I open a "standalone" .php file (in other words, one that is not contained within a Nova "project" folder), it will always use the PEAR standard, regardless of what I have set in the global settings for the extension in the Extension Library.
> [...]
> "Specifically, that preference issue is centered here: https://git.sr.ht/~reykjalin/nova-phpcs/tree/main/item/phpcs.novaextension/Scripts/environment.js#L177
> config.selectedStandard() will never return a falsy value."

Thanks for reporting the issue! Logan’s explanation would certainly make it so
the configuration doesn’t work. I’ll try to fix the issue this week, if I have
the time :)

-Kristófer R.

Happy to hear that helped! Let me know if you run into any further
issues :)

-Kristófer R.

Hi Ash!

> In the extension's settings, I have specified WordPress as the
> Standard.
> 
> […]
> 
> Any ideas on where this could be going wrong?

Is this in the Extension settings or Project settings? The Extension settings
are used to set the default standard - the standard used before you change the
project settings - while the project settings are the "authoritative" source.

I probably need to label the settings in a better way so this is clearer.

> 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.