microsoft / microsoft/tolerant-php-parser
Future tooling plans?
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 894
- Forks
- 85
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 3
Description
Not sure if you're at liberty to discuss at this point, but related to https://github.com/Microsoft/tolerant-php-parser/issues/36#issuecomment-274563749, I was wondering if you had future plans in the PHP tooling space. Will you be building an "official" language server on top of this parser for vscode (or other LSP clients)? Tooling for PHP devs that use vim (or similar) is just abysmal at this point, and it would be awesome to be able to be reasonably productive in vim again!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked issue #36 comment and the repository description for context on IDE tooling. The issue does not name an implementation entry point, files, or tests; done would first require a decided and scoped plan for an official PHP language server for VS Code or other LSP clients.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, vim, vscode
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100