Skip to content
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

bug: fsautocomplete types out of date #34

Open
3 tasks done
WillEhrendreich opened this issue Jul 9, 2023 · 0 comments
Open
3 tasks done

bug: fsautocomplete types out of date #34

WillEhrendreich opened this issue Jul 9, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@WillEhrendreich
Copy link

Did you check docs and existing issues?

  • I have read all the neoconf.nvim docs
  • 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 colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "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
@WillEhrendreich WillEhrendreich added the bug Something isn't working label Jul 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant