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

require('module') doesn't respect relative path for diagnostic in 3.0 #1034

Closed
kevinhwang91 opened this issue Apr 11, 2022 · 0 comments
Closed
Labels
bug Something isn't working

Comments

@kevinhwang91
Copy link
Contributor

kevinhwang91 commented Apr 11, 2022

Describe the bug
Make diagnostic wrong.

To Reproduce
Steps to reproduce the behavior:

  1. Build an ENV below
  2. Run client the server

Input: tree:
Output:

.
└── depth1
    └── foo.lua

1 directory, 1 file

Input: cat depth1/foo.lua
Output:

local M = {}

function M.init()
    return 'init'
end

function M.test()
    require('foo').init(2) -- The function takes only 0 parameters, but you passed 1.
    require('depth1.foo').init()
end

return M

Expected behavior
require('foo').init(2) keep silent

Environment (please complete the following information):

  • OS: ArchLinux
  • Client: Neovim with coc.nvim
@sumneko sumneko added the bug Something isn't working label Apr 11, 2022
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

2 participants