3.x Release

[tm1000]

3.x

See related: vimeo/psalm#8960

Tasks

• Restore Add Psalm config initialization if none found #20
• Fix husky to actually do something
• Merge WIP: Performance/Feature Improvements to the Language Server vimeo/psalm#8960 into https://github.com/vimeo/psalm
  • Allow changing configuration on the fly
  • Address Hide warnings #16 with PR in Upstream

[0x00A1FA]

Hello! How may I help? Can you outline a roadmap?

[tm1000]

@0x00A1FA there you go I put up a roadmap. I just moved the stuff from 2.5 (now that we are on 2.7) into this and additionall marked that 3.x depends on my branch being merged into master (when I get to that)

[0x00A1FA]

Hi,

Any news on this?

Thanks for putting up the roadmap, but I just couldn't work on this myself.

Have a good one.

[tm1000]

Hey @0x00A1FA

What specifically would you want done in the list? Just curious as I don't hear from users much :)

[0x00A1FA]

Hi sir,

Well, besides performance improvements, not much else.

The real issues are recognizing methods that may be hard to analyze. For example, a lot of Laravel queries (I'd appreciate if you could please explain why).

I'm sorry, but this extension is unusable in larger projects right now.

Thank you!

[tm1000]

I don't have much control over that from the extension and it's really no fault of the extension either.

The performance problems you are mentioning are inside of psalm itself. Which was never written to be a language server. That is not its focus and thus its slow at responding.

I assume you are using the composer package for psalm-laravel and ide-helper. Psalm can use those.