@[email protected]

PHP Introspection and Refactoring tool. Helps text editors.

[@[email protected] @phpactor]

As Twitter is removing Tweetdeck and has already removed API access I am no longer going to support Twitter a communication channel.

For latest news you can follow Phpactor on Mastodon: https://t.co/v3N5kwPzJq

[にゃんだーすわん @tadsan]

Congrats! Support for Phar distribution is a great milestone for Phpactor!

[@[email protected] @phpactor]

Tagged a June release:

https://t.co/5MkWGd1czf

Some features and lots of improvements and bug fixes, and now available as a PHAR!

[@[email protected] @phpactor]

Added a diagnostic / code action to automatically add missing `extends` and `implements` generic tags. Can't upload the video here due to issues, but I'm sure you can imagine it!

[@[email protected] @phpactor]

New Phpactor "release" and blog post: https://t.co/VmY2gOpfLy

[Flávio Heleno @flavioheleno]

I think @phpactor is by far one of the most important tools I use on my daily activities. its LSP integration to @sublimehq spots issues on the fly and makes my life a lot easier. kudos to #PHP community <3

[@[email protected] @phpactor]

Merged experimental support for Inlay Hints to `master`, you can enable it via. config:

https://t.co/EE89QFozRY

[@[email protected] @phpactor]

@sitedyno hm, it will effectively create a `.phpactor.json` now for every project. Is that an issue? Maybe it the "auto configure" could be disabled in (global) config.

[@[email protected] @phpactor]

Phpactor provides a fair number of built-in extensions, and now it will automatically suggest them if they apply to your project:

[@[email protected] @phpactor]

Now you can promote constructor properties:

[@[email protected] @phpactor]

Added a new option `language_server.diagnostic_outsource` which will run diagnostics in a separate process. It's disabled by default for now, if you have performance issues, enable it!

[@[email protected] @phpactor]

Introduced (long due) support for hierarchical name completion:

[@[email protected] @phpactor]

Another month of Phpactor (2023 release):

https://t.co/nsdaqskPjF

[@[email protected] @phpactor]

Added naive support for `@param` tag generation

[@[email protected] @phpactor]

Christmas Phpactor (2022.12.12): https://t.co/E3nfZyIqEm

[@[email protected] @phpactor]

@minompi in anycase, one of the limitations with php-cs-fixer currently is that you can't apply it to a range, which would be possible if implementing a dumbish "default" CS fixer.

[@[email protected] @phpactor]

@minompi hm possibly, but even then probably you'd want to create a `.php_cs_fixer.php` config file for your project, and by that point you should probably just install it as a dependency.

I can imagine it's useful to have OOTB behavior for more trivial/non-project coding though.

[@[email protected] @phpactor]

@minompi yeah, well Rust uses Rust fmt, and Go similar. They are external tools but kinda sorta built-in.

We probably could create a basic CS fixer (indentation etc), but not sure where we would define it's limits as I don't want to be the maintainer of a CS fixer really :D

[@[email protected] @phpactor]

@minompi (assume you know about the existing `php-cs-fixer` integration)

[@[email protected] @phpactor]

@minompi anything is possible, but it's really a question of what benefit there would be in basically writing another CS fixer.

basically every project should probably have a CS fixer in the pipeline, so it makes sense to use that one rather than anything Phpactor could reinvent?