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
I am using VS Code with extension reason-vscode Reason Language Server (RLS).
I cloned the re-web demo application with git clone https://github.com/yawaramin/fullstack-reason.git test01. OCaml native backend end NPM reason frontend both work very well, this is very encouraging :)
The non-critical problem: In file backend/App.re, when I navigate to open ReWeb; (see screenshot), reWeb.ml is opened. Starting from here, I can't lookup the symbols because of "No root directory found" in VS Code's error message.
The problem does not relate to ReWeb directly, sure the origin lies more in Reason Language Server's handling of native esy compiled ocaml-files, but I could find a solution yet.
If anybody have found an work-around, please let me know.
No problem if you close this issue, then it could be used for reference reasons - then perhaps it helps other people wanting get in touch ReWeb and search a way around this problem.
Following RLS issues are relating (not solved yet): 162, 177, 334
The text was updated successfully, but these errors were encountered:
I am using
VS Code
with extensionreason-vscode
Reason Language Server (RLS).I cloned the
re-web
demo application withgit clone https://github.com/yawaramin/fullstack-reason.git test01
. OCaml native backend end NPM reason frontend both work very well, this is very encouraging :)The non-critical problem: In file
backend/App.re
, when I navigate toopen ReWeb;
(see screenshot),reWeb.ml
is opened. Starting from here, I can't lookup the symbols because of "No root directory found" inVS Code
's error message.The problem does not relate to ReWeb directly, sure the origin lies more in Reason Language Server's handling of native
esy
compiled ocaml-files, but I could find a solution yet.If anybody have found an work-around, please let me know.
No problem if you close this issue, then it could be used for reference reasons - then perhaps it helps other people wanting get in touch ReWeb and search a way around this problem.
Following RLS issues are relating (not solved yet): 162, 177, 334
The text was updated successfully, but these errors were encountered: