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 have searched the existing issues of neoconf.nvim
I have searched the existing issues of plugins related to this issue
Neovim version (nvim -v)
NVIM v0.10.0 ***
Operating system/version
Windows 10
Describe the bug
hey, I noticed that the types are not being correctly updated with the language server fsautocomplete.
they just added
"FSharp.fsac.sourceTextImplementation": {
"default": "NamedText",
"description": "EXPERIMENTAL. Enables the use of a new source text implementation. This may have better memory characteristics. Requires restart.",
"enum": [
"NamedText",
"RoslynSourceText"
]
},
in between
"FSharp.fsac.netCoreDllPath": {
"default": "",
"description": "The path to the \u0027fsautocomplete.dll\u0027, a directory containing TFM-specific versions of fsautocomplete.dll, or a directory containing fsautocomplete.dll. Useful for debugging a self-built FSAC. If a DLL is specified, uses it directly. If a directory is specified and it contains TFM-specific folders (net6.0, net7.0, etc) then that directory will be probed for the best TFM to use for the current runtime. This is useful when working with a local copy of FSAC, you can point directly to the bin/Debug or bin/Release folder and it\u0027ll Just Work. Finally, if a directory is specified and there are no TFM paths, then fsautocomplete.dll from that directory is used. Requires restart.",
"scope": "machine-overridable",
"type": "string"
},
"FSharp.fsac.sourceTextImplementation": {
"default": "NamedText",
"description": "EXPERIMENTAL. Enables the use of a new source text implementation. This may have better memory characteristics. Requires restart.",
"enum": [
"NamedText",
"RoslynSourceText"
]
},
"FSharp.fsac.parallelReferenceResolution": {
"default": false,
"description": "EXPERIMENTAL: Speed up analyzing of projects in parallel. Requires restart.",
"type": "boolean"
},
I looked at the github actions for the repo and see there have been some failing ones. that might be part of what's going on.
Steps To Reproduce
it's not really a steps thing i don't think.
Expected Behavior
that the types would be correctly auto generated.
Repro
-- I don't think doing a minimal repro will likely help the situation, so I haven't changed anything here. -- DO NOT change the paths and don't remove the colorschemelocalroot=vim.fn.fnamemodify("./.repro", ":p")
-- set stdpaths to use .reprofor_, nameinipairs({ "config", "data", "state", "cache" }) dovim.env[("XDG_%s_HOME"):format(name:upper())] =root.."/" ..nameend-- bootstrap lazylocallazypath=root.."/plugins/lazy.nvim"ifnotvim.loop.fs_stat(lazypath) thenvim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
endvim.opt.runtimepath:prepend(lazypath)
-- install pluginslocalplugins= {
"folke/tokyonight.nvim",
"folke/neoconf.nvim",
-- add any other plugins here
}
require("lazy").setup(plugins, {
root=root.."/plugins",
})
vim.cmd.colorscheme("tokyonight")
-- add anything else here
The text was updated successfully, but these errors were encountered:
Just came across this while looking for issues that #63 would resolve - @WillEhrendreich is this still an issue? FSharp.fsac.sourceTextImplementation is now present, and the auto-generation seems to be working properly.
You know, I don't think it's an issue anymore, but I haven't checked it in a while, officially. Been a little while since I was doing a lot of daily dev on github.com/WillEhrendreich/Ionide-nvim , so the nitty gritty details of what config properties are being added or changed has been under my radar as of the last few months.
Did you check docs and existing issues?
Neovim version (nvim -v)
NVIM v0.10.0 ***
Operating system/version
Windows 10
Describe the bug
hey, I noticed that the types are not being correctly updated with the language server fsautocomplete.
they just added
in between
I looked at the github actions for the repo and see there have been some failing ones. that might be part of what's going on.
Steps To Reproduce
it's not really a steps thing i don't think.
Expected Behavior
that the types would be correctly auto generated.
Repro
The text was updated successfully, but these errors were encountered: