#phpactor — Public Fediverse posts

Using @phpactor as a language server for WordPress development

by @dvk

https://www.dannyvankooten.com/blog/2026/using-phpactor-with-wordpress/

#PHPActor #PHP #WordPress

Using @phpactor as a language server for WordPress development

by @dvk

https://www.dannyvankooten.com/blog/2026/using-phpactor-with-wordpress/

#PHPActor #PHP #WordPress

Using @phpactor as a language server for WordPress development

by @dvk

https://www.dannyvankooten.com/blog/2026/using-phpactor-with-wordpress/

#PHPActor #PHP #WordPress

Using @phpactor as a language server for WordPress development

by @dvk

https://www.dannyvankooten.com/blog/2026/using-phpactor-with-wordpress/

#PHPActor #PHP #WordPress

Using @phpactor as a language server for WordPress development

by @dvk

https://www.dannyvankooten.com/blog/2026/using-phpactor-with-wordpress/

#PHPActor #PHP #WordPress

#phpactor is clearly not understanding the assignment :-/

#missingThePoint #PHP

#phpactor is clearly not understanding the assignment :-/

#missingThePoint #PHP

#phpactor is clearly not understanding the assignment :-/

#missingThePoint #PHP

#phpactor is clearly not understanding the assignment :-/

#missingThePoint #PHP

#phpactor is clearly not understanding the assignment :-/

#missingThePoint #PHP

#phpactor vs #intelephense

This was a useful summary
https://yarnaudov.com/phpactor-vs-intelephense.html

Although last time I did this test phpactor's performance noticeably lagged and that post does not talk about performance at all. I *want* to use phpactor because it's #openSource

Which is best for you and what do you like about it? There's PHPStan too but I'm never sure if that's something different or an equivalent. Boosts welcome

#php #IDE #webDev

#phpactor vs #intelephense

This was a useful summary
https://yarnaudov.com/phpactor-vs-intelephense.html

Although last time I did this test phpactor's performance noticeably lagged and that post does not talk about performance at all. I *want* to use phpactor because it's #openSource

Which is best for you and what do you like about it? There's PHPStan too but I'm never sure if that's something different or an equivalent. Boosts welcome

#php #IDE #webDev

#phpactor vs #intelephense

This was a useful summary
https://yarnaudov.com/phpactor-vs-intelephense.html

Although last time I did this test phpactor's performance noticeably lagged and that post does not talk about performance at all. I *want* to use phpactor because it's #openSource

Which is best for you and what do you like about it? There's PHPStan too but I'm never sure if that's something different or an equivalent. Boosts welcome

#php #IDE #webDev

#phpactor vs #intelephense

This was a useful summary
https://yarnaudov.com/phpactor-vs-intelephense.html

Although last time I did this test phpactor's performance noticeably lagged and that post does not talk about performance at all. I *want* to use phpactor because it's #openSource

Which is best for you and what do you like about it? There's PHPStan too but I'm never sure if that's something different or an equivalent. Boosts welcome

#php #IDE #webDev

#phpactor vs #intelephense

This was a useful summary
https://yarnaudov.com/phpactor-vs-intelephense.html

Although last time I did this test phpactor's performance noticeably lagged and that post does not talk about performance at all. I *want* to use phpactor because it's #openSource

Which is best for you and what do you like about it? There's PHPStan too but I'm never sure if that's something different or an equivalent. Boosts welcome

#php #IDE #webDev

Probably the biggest issue for me is that when using #helix with #phpactor auto completing variables always results in two dollar signs, which is incredibly annoying for obvious reasons. I am going to write an issue about this the next days, since this is obviously a bug (not sure if in #helix or #phpactor though). But there are also other things missing.

Probably the biggest issue for me is that when using #helix with #phpactor auto completing variables always results in two dollar signs, which is incredibly annoying for obvious reasons. I am going to write an issue about this the next days, since this is obviously a bug (not sure if in #helix or #phpactor though). But there are also other things missing.

Probably the biggest issue for me is that when using #helix with #phpactor auto completing variables always results in two dollar signs, which is incredibly annoying for obvious reasons. I am going to write an issue about this the next days, since this is obviously a bug (not sure if in #helix or #phpactor though). But there are also other things missing.

Probably the biggest issue for me is that when using #helix with #phpactor auto completing variables always results in two dollar signs, which is incredibly annoying for obvious reasons. I am going to write an issue about this the next days, since this is obviously a bug (not sure if in #helix or #phpactor though). But there are also other things missing.

Probably the biggest issue for me is that when using #helix with #phpactor auto completing variables always results in two dollar signs, which is incredibly annoying for obvious reasons. I am going to write an issue about this the next days, since this is obviously a bug (not sure if in #helix or #phpactor though). But there are also other things missing.

An observation: #phpactor is nifty but also often inaccurate.

(in this case: claiming an imported interface is never used, when in fact it is used in an is_subclass_of() check about a dozen lines later. It's also grousing about a called method in a trait not being declared in that same trait... but that's the thing about traits: there's no syntax to say "this trait should only be used by class X" or "this trait implements interface Y"... and if you declare the method as abstract, PHP might scream "collision!" when you use the trait. ...or is that only for non-abstract methods? Anyway, it gets ambiguous for me, so I avoid doing that.)

An observation: #phpactor is nifty but also often inaccurate.

(in this case: claiming an imported interface is never used, when in fact it is used in an is_subclass_of() check about a dozen lines later. It's also grousing about a called method in a trait not being declared in that same trait... but that's the thing about traits: there's no syntax to say "this trait should only be used by class X" or "this trait implements interface Y"... and if you declare the method as abstract, PHP might scream "collision!" when you use the trait. ...or is that only for non-abstract methods? Anyway, it gets ambiguous for me, so I avoid doing that.)

An observation: #phpactor is nifty but also often inaccurate.

(in this case: claiming an imported interface is never used, when in fact it is used in an is_subclass_of() check about a dozen lines later. It's also grousing about a called method in a trait not being declared in that same trait... but that's the thing about traits: there's no syntax to say "this trait should only be used by class X" or "this trait implements interface Y"... and if you declare the method as abstract, PHP might scream "collision!" when you use the trait. ...or is that only for non-abstract methods? Anyway, it gets ambiguous for me, so I avoid doing that.)

An observation: #phpactor is nifty but also often inaccurate.

(in this case: claiming an imported interface is never used, when in fact it is used in an is_subclass_of() check about a dozen lines later. It's also grousing about a called method in a trait not being declared in that same trait... but that's the thing about traits: there's no syntax to say "this trait should only be used by class X" or "this trait implements interface Y"... and if you declare the method as abstract, PHP might scream "collision!" when you use the trait. ...or is that only for non-abstract methods? Anyway, it gets ambiguous for me, so I avoid doing that.)

An observation: #phpactor is nifty but also often inaccurate.

(in this case: claiming an imported interface is never used, when in fact it is used in an is_subclass_of() check about a dozen lines later. It's also grousing about a called method in a trait not being declared in that same trait... but that's the thing about traits: there's no syntax to say "this trait should only be used by class X" or "this trait implements interface Y"... and if you declare the method as abstract, PHP might scream "collision!" when you use the trait. ...or is that only for non-abstract methods? Anyway, it gets ambiguous for me, so I avoid doing that.)

@phpactor How do I disable some diagnostic features in phpactor? I tried adding this to my phpactor.json to no effect:

"diagnostics.undefined_variable.enabled": false,
"diagnostics.unresolvable_name.enabled": false

The Diagnostics page doesn't mention how to use these keywords in the config file. https://phpactor.readthedocs.io/en/master/reference/diagnostic.html

#phpactor

@phpactor How do I disable some diagnostic features in phpactor? I tried adding this to my phpactor.json to no effect:

"diagnostics.undefined_variable.enabled": false,
"diagnostics.unresolvable_name.enabled": false

The Diagnostics page doesn't mention how to use these keywords in the config file. https://phpactor.readthedocs.io/en/master/reference/diagnostic.html

#phpactor

@phpactor How do I disable some diagnostic features in phpactor? I tried adding this to my phpactor.json to no effect:

"diagnostics.undefined_variable.enabled": false,
"diagnostics.unresolvable_name.enabled": false

The Diagnostics page doesn't mention how to use these keywords in the config file. https://phpactor.readthedocs.io/en/master/reference/diagnostic.html

#phpactor

@phpactor How do I disable some diagnostic features in phpactor? I tried adding this to my phpactor.json to no effect:

"diagnostics.undefined_variable.enabled": false,
"diagnostics.unresolvable_name.enabled": false

The Diagnostics page doesn't mention how to use these keywords in the config file. https://phpactor.readthedocs.io/en/master/reference/diagnostic.html

#phpactor

@phpactor How do I disable some diagnostic features in phpactor? I tried adding this to my phpactor.json to no effect:

"diagnostics.undefined_variable.enabled": false,
"diagnostics.unresolvable_name.enabled": false

The Diagnostics page doesn't mention how to use these keywords in the config file. https://phpactor.readthedocs.io/en/master/reference/diagnostic.html

#phpactor

TIL that `$http_response_headers` is a magic variable that magically appears in the local scope when you use a HTTP wrapper in PHP 😍 it's the sort of thing I want to say "won't fix" for in #phpactor

TIL that `$http_response_headers` is a magic variable that magically appears in the local scope when you use a HTTP wrapper in PHP 😍 it's the sort of thing I want to say "won't fix" for in #phpactor

TIL that `$http_response_headers` is a magic variable that magically appears in the local scope when you use a HTTP wrapper in PHP 😍 it's the sort of thing I want to say "won't fix" for in #phpactor

TIL that `$http_response_headers` is a magic variable that magically appears in the local scope when you use a HTTP wrapper in PHP 😍 it's the sort of thing I want to say "won't fix" for in #phpactor

TIL that `$http_response_headers` is a magic variable that magically appears in the local scope when you use a HTTP wrapper in PHP 😍 it's the sort of thing I want to say "won't fix" for in #phpactor

@godlike I'm currently switching between #Intelephense (paid) and #PHPActor -- I'd love a combination of both. :)

@godlike I'm currently switching between #Intelephense (paid) and #PHPActor -- I'd love a combination of both. :)

@godlike I'm currently switching between #Intelephense (paid) and #PHPActor -- I'd love a combination of both. :)

@godlike I'm currently switching between #Intelephense (paid) and #PHPActor -- I'd love a combination of both. :)

@godlike I'm currently switching between #Intelephense (paid) and #PHPActor -- I'd love a combination of both. :)

@dantleech @phpactor

I've set up #neovim with #phpactor (p) and another with #intelephense (i) I used Mason to install each.

What I noticed:

- The calculated root_dir fails for (p); it uses PWD

- BOTH give me signature help and completions (p) is slower and seems to crash on providing signatures for completion.

- BOTH let me jump to definition, though (i) is noticeably faster at this.

- Far fewer diagnostics from phpactor (no static analysis? Perhaps I need to add PHPStan as well?)

@dantleech @phpactor

I've set up #neovim with #phpactor (p) and another with #intelephense (i) I used Mason to install each.

What I noticed:

- The calculated root_dir fails for (p); it uses PWD

- BOTH give me signature help and completions (p) is slower and seems to crash on providing signatures for completion.

- BOTH let me jump to definition, though (i) is noticeably faster at this.

- Far fewer diagnostics from phpactor (no static analysis? Perhaps I need to add PHPStan as well?)

@dantleech @phpactor

I've set up #neovim with #phpactor (p) and another with #intelephense (i) I used Mason to install each.

What I noticed:

- The calculated root_dir fails for (p); it uses PWD

- BOTH give me signature help and completions (p) is slower and seems to crash on providing signatures for completion.

- BOTH let me jump to definition, though (i) is noticeably faster at this.

- Far fewer diagnostics from phpactor (no static analysis? Perhaps I need to add PHPStan as well?)

@dantleech @phpactor

I've set up #neovim with #phpactor (p) and another with #intelephense (i) I used Mason to install each.

What I noticed:

- The calculated root_dir fails for (p); it uses PWD

- BOTH give me signature help and completions (p) is slower and seems to crash on providing signatures for completion.

- BOTH let me jump to definition, though (i) is noticeably faster at this.

- Far fewer diagnostics from phpactor (no static analysis? Perhaps I need to add PHPStan as well?)

@dantleech @phpactor

I've set up #neovim with #phpactor (p) and another with #intelephense (i) I used Mason to install each.

What I noticed:

- The calculated root_dir fails for (p); it uses PWD

- BOTH give me signature help and completions (p) is slower and seems to crash on providing signatures for completion.

- BOTH let me jump to definition, though (i) is noticeably faster at this.

- Far fewer diagnostics from phpactor (no static analysis? Perhaps I need to add PHPStan as well?)

#phpactor is fast enough for me on most projects, but I tried contributing to PHPstan the other day and it was unusable (big, complicated files). So going to invest some time into making it more efficient. Esp. now I'm temporarily liberated from work responsibilities :D

#phpactor is fast enough for me on most projects, but I tried contributing to PHPstan the other day and it was unusable (big, complicated files). So going to invest some time into making it more efficient. Esp. now I'm temporarily liberated from work responsibilities :D

#phpactor is fast enough for me on most projects, but I tried contributing to PHPstan the other day and it was unusable (big, complicated files). So going to invest some time into making it more efficient. Esp. now I'm temporarily liberated from work responsibilities :D

#phpactor is fast enough for me on most projects, but I tried contributing to PHPstan the other day and it was unusable (big, complicated files). So going to invest some time into making it more efficient. Esp. now I'm temporarily liberated from work responsibilities :D

🆗 some follow ups. I've uninstalled the #intelephense npm package and I'm now connecting to #lsp provided by #phpactor installed globally.

Sadly I wasn't able to use felixfbecker/language-server (as described in docs) since it's development is discontinued and it is not #php8 compatible.

https://develop.spacemacs.org/layers/+lang/php/README.html

I'm still missing completion and probably some other functionalities I'm unaware of.

If only I'd find & fix the intelephense issue 🙏 .