IssueRaiser

Please give extensions access to native AST tokens (At least partially)

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ --> <!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ --> <!-- Please search existing issues to avoid creating duplicates. --> <!-- Describe the feature you'd like. --> This feature request is very similar to this: https://github.com/microsoft/vscode/issues/131062 **But now I want to reintroduce it with very updated and very carefully thought reasoning.** Even though you might think that this feature request is too much (too unreal, too hard) to implement, I think it's worth to try because of the reasonings down below: 1] There are already too many VS Code extensions which need some access to the AST tree of editor code, and they don't have native access, so they use third party (or custom) libraries. And when syntaxes of languages get updated, they need to find new libraries (if current libraries don't keep up with the updates). And there are so many languages, so this process sooner or later will become unmanageable. VS Code probably always will have latest tokenizers/parsers natively, so let's just give extension developers access to those native AST tokens (at least partially, if not full AST). 2] One good example of such extensions is my creation <a href="https://marketplace.visualstudio.com/items?itemName=leodevbro.blockman">Blockman</a>, which has already **117K installs** and the number increases by 100-200 every day. Blockman (<a href="https://www.youtube.com/watch?

Posted by leodevbro on Mar 17, 2023, 10:34 AM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.2,500 issues0 comments

reliability (Software)

Please give extensions access to native AST tokens (At least partially)

leodevbroMar 17, 2023, 10:34 AM

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ --> <!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ --> <!-- Please search existing issues to avoid creating duplicates. --> <!-- Describe the feature you'd like. --> This feature request is very similar to this: https://github.com/microsoft/vscode/issues/131062 **But now I want to reintroduce it with very updated and very carefully thought reasoning.** Even though you might think that this feature request is too much (too unreal, too hard) to implement, I think it's worth to try because of the reasonings down below: 1] There are already too many VS Code extensions which need some access to the AST tree of editor code, and they don't have native access, so they use third party (or custom) libraries. And when syntaxes of languages get updated, they need to find new libraries (if current libraries don't keep up with the updates). And there are so many languages, so this process sooner or later will become unmanageable. VS Code probably always will have latest tokenizers/parsers natively, so let's just give extension developers access to those native AST tokens (at least partially, if not full AST). 2] One good example of such extensions is my creation <a href="https://marketplace.visualstudio.com/items?itemName=leodevbro.blockman">Blockman</a>, which has already **117K installs** and the number increases by 100-200 every day. Blockman (<a href="https://www.youtube.com/watch?

Comments (0)

No comments yet. Start the discussion.

Comment on this issue