-
-
Notifications
You must be signed in to change notification settings - Fork 331
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
Doc export file paths all start with ile://
#2971
Comments
Ah...
|
We are currently working on a full documentation export for a large RTS engine, so it should be a good test case. Is there a prior release version we can try rolling back to to compare doc export before this PR was merged? |
I can't work out how to install a historic version with brew.
Is this possible? |
Okay, I just installed directly from the GitHub releases. I can confirm that this version does not have the above issue, and also fixes #2977. It seems this PR may have introduced a number of issues. |
I just took some time to debug into this, found the logic that causing this issue, but have yet come up with a good solution 😕
I believe this logic intends to remove the path prefix, such that each paths in the output are relative to the supplied directory. For example:
Now you may think that we can simply pass Workaround 1
lua-language-server --doc=$PWD --doc_out_path docs/ => each file path will now be
lua-language-server --doc=$PWD/ --doc_out_path docs/ => each file path will now be Workaround 2Judging from the diff in #2821, the original handling of file name is just to use
...
"docScriptPath": "export.lua"
function export.getLocalPath(uri)
return uri
end
lua-language-server --doc=$PWD/ --doc_out_path docs/ => now you should have the classic uri result |
How are you using the lua-language-server?
Command Line
Which OS are you using?
Windows WSL
What is the issue affecting?
Other
Expected Behaviour
Paths in exported doc JSON should start with
file:///
as in the example:Actual Behaviour
Missing the leading
f
:Reproduction steps
Additional Notes
How do you get a version?
Log File
No response
The text was updated successfully, but these errors were encountered: