search

jeapostrophe / racket-langserver

Other
271 stars 24 forks source link

Good first issue? #8

Open Eugleo opened 5 years ago

Eugleo commented 5 years ago

Hey, is the project alive? I'd love to get involved, but I don't have much experience with racket (nor LSPs, for that matter). Could you point me to some good issues/places to start reading the code or give me some tips on how to start?

Also, what is the difference between this and https://github.com/theia-ide/racket-language-server/ ?

jeapostrophe commented 5 years ago

It is alive.

The other one started by someone looking at our implementation and deciding they wanted to do it differently and they forked and re-wrote a lot of stuff.

Eugleo commented 5 years ago

Great to hear that, thanks! And what about the entry points? Is there any work to be done suitable for a intermediate racketeer?

Eugleo commented 4 years ago

Hey, I decided to revive this old issue. I've gotten requests to integrate code formatting into my vscode extension magic-racket, and you have that listed as WIP as well.

I think it might be beneficial if I helped you to finish it off, instead of running with my own implementation (if you want/need some help, that is). @JJpro helped me to integrate your language server into the extension, so now the last thing that needs to be done is actually finish the feature in you LSP.

So, would you mind giving me some pointers on what is done, what needs to be done, and what to watch out for, in the context of document/selection formatting? Also, the old question still stands; if you've got any general insights about contributing to this project, I'd love to hear them.

jeapostrophe commented 4 years ago

I think that the right way to implement most features in Racket-LSP is to find the corresponding feature in DrRacket and then disentangle from DrR's GUI and then expose the feature through the LSP. In many cases, DrR has already been internally organized to do that, but we just haven't done enough spelunking yet.

jryans commented 1 year ago

I think this issue could be closed... It seems like the questions above have been answered.

spdegabrielle commented 1 year ago

PR to add advice from @jeapostrophe into README.md --> #99