New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature list or Roadmap #6
Comments
I don't have either yet, I'll have a think 👍 but I'm very open to ideas! Right now I think it needs to be tested against some codebases, I updated all the deps and tests. Thinks are working, but some things are probably broken. |
@orta how would one go about testing this against some codebase? I'm setting up a TS/Svelte monorepo and would be happy to try out a few different use-cases with this, but I don't know how to set up language servers. Do you have some links/info that can get me started in the right direction? |
Good thinking @joelmukuthu - I've just shipped a PR which makes the docs a lot more explicit about how to get up and running #10 |
It would be great to have intellisense features:
@alexprey has done foundations work for this by creating https://github.com/alexprey/sveltedoc-parser, a parser for svelte files which outputs infos about them in a readable json format. @ArdenIvanov has built a language server / VSCode extension on top of it https://github.com/ArdenIvanov/svelte-intellisense . Maybe we could integrate their works into this project. |
Yep, I'm open to migrating all of these sorts of features in - yep! |
A feature list with what's done and what's not is now available at #83 |
Maybe we need that to work with the community.
The text was updated successfully, but these errors were encountered: