pylyzer should report relative file path in original case

[rtgiskard]

I'm using neovim with plugin like telescope and trouble, pylyzer is installed with mason as lsp server.

pylyzer installed version: 0.0.31 my neovim config: lazyNvim

• here is an case

  mkdir Ac
  cat >>Ac/tesT.py <<EOF
  import os
  abc = defg
  EOF
  
  # open with nvim
  nvim Ac/tesT.py

  within nvim, check lsp info with :LspInfo, get:

   ..
  Config: pylyzer
      filetypes:         python
      root directory:    Not found.
  ..

  pylyzer seems not load at the time as root directory not found, while pyright run in single file mode by default for the case

  to load pylyzer, run: touch Ac/pyproject.toml, then open the py file with nvim Ac/tesT.py, pylyzer should run with a known root directory.

  within nvim, check the diagnostic list with :TroubleToggle

  

  the last item is reported by pylyzer, and the reported path is 'ac/test.py' which should be 'Ac/tesT.py', for which preview with trouble or telescope will fail for unable to find the file.

  then exit nvim and change dir: cd Ac; nvim tesT.py, check again

  pylyzer use full path in lowered case, while pyright use relative path, and the same issue for other tools.

• the issue

  1. pylyzer report with lower cased path, relative path with orignal case should be fine
  2. pylyzer seems to analyze with file instead of the buffer content, for which without save to file, the report will not update

[mtshiba]

All issues have been fixed in v0.0.36. Also, although it is trivial, the source of the error (program name "pylyzer") is now displayed.

[DanielAndreasen]

Is the pyproject.toml required for pylyzer to run? I have a very similar experience as above in nvim with latest pylyzer version (0.0.39). Nothing happened until I touched the toml-file.