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

Inline type hints don't show up after update to 1.11.2 #229

Closed
kamoshi opened this issue Aug 5, 2023 · 4 comments · Fixed by #230
Closed

Inline type hints don't show up after update to 1.11.2 #229

kamoshi opened this issue Aug 5, 2023 · 4 comments · Fixed by #230
Assignees
Labels
bug Something isn't working

Comments

@kamoshi
Copy link

kamoshi commented Aug 5, 2023

Neovim version (nvim -v)

v0.9.1

Operating system/version

Arch Linux

Output of haskell-language-server-wrapper --version

haskell-language-server version: 2.0.0.1 (GHC: 8.10.7) (PATH: /home/kamov/.ghcup/hls/2.0.0.1/lib/haskell-language-server-2.0.0.1/bin/haskell-language-server-wrapper)

How to reproduce the issue

Update haskell-tools from 1.11.1 to 1.11.2

Updated (1)
    ○ haskell-tools.nvim   haskell
        369d81b docs(changelog): release notes (2 days ago)
        a589a80 fix(cabal): prevent error messages caused by external lsp plugins (#224) (2 days ago)
        d38c1b6 style(readme): sloth heading -> paragraph (3 days ago)
        53014f4 fix: hotfix for neovim-nightly compatibility update (3 days ago)
        ca6972d chore: neovim-nightly compatibility update (#222) (3 days ago)
        ff7dad6 chore: use lua-ls from pre-commit-hooks-nix + add type cast (3 days ago)
        070f78d chore: update flake.lock (#220) (13 days ago)
        9bc5409 ci: replace typecheck with lua-ls pre-commit-hook (#219) (3 weeks ago)

Expected behaviour

image

Actual behaviour

image

Log files

No response

The minimal config used to reproduce this issue.

I use the Lazy package manager and the default config in ftplugin/haskell.lua as shown in the README of this project

local lazypath = vim.fn.stdpath("data") .. "/lazy/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",
    "--branch=stable", -- latest stable release
    lazypath,
  })
end
vim.opt.rtp:prepend(lazypath)


require("lazy").setup({
  {
    'mrcjkb/haskell-tools.nvim',
    dependencies = {
      'nvim-lua/plenary.nvim',
      'nvim-telescope/telescope.nvim',
    },
    version = '1.11.2', -- use 1.11.1 to see inline hints working correctly
  }
})
@kamoshi kamoshi added the bug Something isn't working label Aug 5, 2023
kamoshi added a commit to kamoshi/dotfiles that referenced this issue Aug 5, 2023
@mrcjkb
Copy link
Owner

mrcjkb commented Aug 5, 2023

Thanks for reporting this.
I have been able to reproduce it with your config and will investigate.

@mrcjkb mrcjkb self-assigned this Aug 5, 2023
@mrcjkb mrcjkb linked a pull request Aug 5, 2023 that will close this issue
5 tasks
Repository owner deleted a comment from allcontributors bot Aug 5, 2023
Repository owner deleted a comment from allcontributors bot Aug 5, 2023
Repository owner deleted a comment from allcontributors bot Aug 5, 2023
Repository owner deleted a comment from allcontributors bot Aug 5, 2023
@mrcjkb
Copy link
Owner

mrcjkb commented Aug 5, 2023

@all-contributors Please add @kamoshi for bug.

@allcontributors
Copy link
Contributor

@mrcjkb

I've put up a pull request to add @kamoshi! 🎉

mrcjkb added a commit that referenced this issue Aug 5, 2023
Adds @kamoshi as a contributor for bug.

This was requested by mrcjkb [in this
comment](#229 (comment))

[skip ci]

---------

Co-authored-by: allcontributors[bot] <46447321+allcontributors[bot]@users.noreply.github.com>
Co-authored-by: Marc Jakobi <marc@jakobi.dev>
@mrcjkb
Copy link
Owner

mrcjkb commented Aug 5, 2023

Fixed. Thanks for the detailed report @kamoshi 😄

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

Successfully merging a pull request may close this issue.

2 participants