Support for scalar_objects php extension

[still-dreaming-1]

I just started using this extension today, and I am absolutely floored at how well it works! I definitely expect to pay for premium when the free trial runs out. Anyway, the main thing it is lacking for me is, understanding code that utilizes the scalar_objects php extension. This extension enables a syntax where it looks like you can call "methods" on values with built in types, such as string and int. So you can have code like $myString->sub(0, 1); Currently phptools always shows "Call to a member function sub() on a non-object of type stringPHP(PHP0404)" for these calls.

I realize it is a big ask to want support for a specific, non-standard php extension. This php extension is one of the keys to keeping php usable and nice for me. It works well even with php 8.2, and was developed by a well known and respected php developer that is very actively involved in the development of php. He didn't really intend it to be used in production code the way I do, but it seems to work quite well for me, and has been working for some time now.

[jakubmisek]

Hello @still-dreaming-1, and thank you very much for your appreciation!

I agree we should provide a solution for this; I'm adding it to our to-do list.

For now, as a workaround, you can disable PHP0404 error code in your settings.json:

"php.problems.exclude" : {
    "/" : [404],
}

[jakubmisek]

Preparing pre-release with the support for scalar_objects extension, IntelliSense, and code diagnostics for extension methods.

[jakubmisek]

Please try the pre-release (howto: https://docs.devsense.com/en/vscode/installation#pre-release-installation) v1.37.13631.

Also, add the following to your .vscode/settings.json to avoid underlining of register_primitive_type_handler() function call.

    "php.stubs": [
        "*",
        "scalar_objects"
    ]

[still-dreaming-1]

Great! I just added those settings and switched to the pre-release version.

It is no longer showing issues for these calls which is nice.

If I hover over one of these extension method calls, it pops up with the signature information. It shows it literally as it is in the code, showing the initial parameter that is implicit. I'm on the fence on if that is the preferred way or if it would be better if it hid the first parameter since it is implicit. Just something I noticed.

If I edit the code and try to call one of these, it shows information helping me pass in the correct parameters, only the ones after the first parameter (which is implicit). This is super helpful!

It would be very helpful if I could use the "Go To Definition" feature on these, as I use this quite a lot. Currently this doesn't work.

[jakubmisek]

Great! Thank you for trying it so fast.

We'll try to fix the tooltip and go to def.

[still-dreaming-1]

Cool. Inlay hints is also not working yet.

[jakubmisek]

• scalar_objects stubs
• code diagnostics to respect defined methods on scalar types
• code completion with extension methods
• signature help for extension methods
• tool tip of extension method
• inlay hints of called extension methods
• go to def
• occurrence highlighting and refactoring

[jakubmisek]

thank you! I'll do some more testing and prepare a new pre-release.

[still-dreaming-1]

It all works perfectly now, thanks!

[jakubmisek]

@still-dreaming-1 thank you for testing it!