You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looks like you have everything required in the model for performing various code validations, such as type-checking arguments. (Likely, type-inference and scope-based variable type annotations is the main thing missing to support work in that direction.)
Any plans to perform code validations eventually?
Or is that outside the scope of this project?
I realize there are plenty of options for static analysis, but most of the components that do the heavy lifting are very similar to what you've implemented - and none of them were designed as IDE tools, from the top-down with real-time performance in mind.
If we had a framework for this, I'd be happy to help with the actual inspections, so I could finally ditch the PHP storm bug nest and go all-in on VS Code ;-)
The text was updated successfully, but these errors were encountered:
That's the plan. Code validation will be provided by the diagnostics provider. Currently it just reports parse errors. I haven't done much work on this as I'm considering moving to a representation of the syntax tree that is easier to work with (ast instead of parse tree), plus there are improvements to the type inference to be made in cases where phpdoc and type hints are not available for function return type. Any help would be appreciated :)
I'll close this in favour of bmewburn/intelephense#16
Looks like you have everything required in the model for performing various code validations, such as type-checking arguments. (Likely, type-inference and scope-based variable type annotations is the main thing missing to support work in that direction.)
Any plans to perform code validations eventually?
Or is that outside the scope of this project?
I realize there are plenty of options for static analysis, but most of the components that do the heavy lifting are very similar to what you've implemented - and none of them were designed as IDE tools, from the top-down with real-time performance in mind.
If we had a framework for this, I'd be happy to help with the actual inspections, so I could finally ditch the PHP storm bug nest and go all-in on VS Code ;-)
The text was updated successfully, but these errors were encountered: