You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 29, 2021. It is now read-only.
Firstly, been watching this project for a few months now. Looks like it's getting there. Excited for it.
So, I've pulled the master branch of the repo, created the project in Visual Studio, and compiled the package. npm run compile
I then moved the entire cloned folder into the packages section of Atom. I can see the package there, and it is working without errors, though I cannot select is as a language.
In Atom
Folder structure after compile
Language Selection
The text was updated successfully, but these errors were encountered:
This is not an atom extension, it's a general language server for any editor. The fact that it loaded at all without errors shocks me and seems like an atom bug.
For it to work in atom, you would need a project similar to vscode-mcfunction, but for atom.
May I ask what is the mcfunction-langserver folder is, because I don't think that's because of something I've made.
The mcfunction-langserver was created when I loaded up the NJS project in VS. It's empty.
So, that begs the question, how would I use the language server with Atom? The structure of that vscode-mcfunction looks similar to the compiled structure from your repo. Or shall I just wait till' full release?
Hey Levertion,
Firstly, been watching this project for a few months now. Looks like it's getting there. Excited for it.
So, I've pulled the master branch of the repo, created the project in Visual Studio, and compiled the package.
npm run compile
I then moved the entire cloned folder into the packages section of Atom. I can see the package there, and it is working without errors, though I cannot select is as a language.
In Atom
Folder structure after compile
Language Selection
The text was updated successfully, but these errors were encountered: