Replies: 2 comments 3 replies
We already have The problem is that |
|
What is your use case exactly? If you have a rule that explicitly sets I’m open to extending the interface to return Are you using remark / rehype / retext / redot / MDX? Something else? What should be considered public interface to support this? Could we even implement new API calls without a major version release if we expose this? Should we even call |
Uh oh!
There was an error while loading. Please reload this page.
First of all thanks for the great libraries 🎩
I'm currently playing with unified-language-server.
While using it I notice that I needed some changes, but maybe those can be beneficial to others.
I'm not sure reflect the direction but if needed I can create Issues and/or PRs.
So here are the list of changes that I got so far:
I export
unistLocationToLspRangeThis is handy because I can use manually create Diagnostic from node.
If the
messagecontains aDiagnosticI return the diagnostic invfileMessageToDiagnosticThis is useful because I can pass custom Diagnostic that I create my self with
VFile.MessageandObject.assign.Return the
connectionanddocumentsfrom the constructor.This allows me to complete my implementation and implement extra features such as
onCompletitionoronCodeActionResolveI accept an argument
onCodeActiona callback that if return an handler then doesn't continue with the parsing of theDiagnostic.I currently hard-code my requirements for
capabilitiesinonInitialize, but I will believe that this can also be pass as an option.Please feel free to cherry-pick or discard any of the above proposal,
but if you accept my contribution I will be happy to help.
All reactions