Fix internal errors propagating to stderr

[AlexandrosAlexiou]

• Log analyze errors instead of throwing exceptions that propagate to stderr and trigger Neovim pop-up messages when using noice.nvim plugin.
  • Implement general code improvements (visibility modifiers, add explicit types, use val instead of var, default function params)
  • Fix tests
  • Remove unused imports

[owl-from-hogvarts]

LGTM. Except, instead of propagating error we are propagating null value now. What is the end result of the null propagation? I see that it results in nulls being displayed in user interface at least somewhere

[owl-from-hogvarts]

@AlexandrosAlexiou Notifying you, that our organisation has changed name as of your suggestion. Please, update remote repo url in your local clone

[AlexandrosAlexiou]

LGTM. Except, instead of propagating error we are propagating null value now. What is the end result of the null propagation? I see that it results in nulls being displayed in user interface at least somewhere

Which user interface are you referring to? AFAIK, an exception will only print to stderr if it is not caught, here we catch it we log the error and return null from the function. Please correct me if I am wrong.

[owl-from-hogvarts]

Speaking of GUI, I referred to Hower.kt:30. But, after more thoroughly reviewing code I can confirm, that null won't get into UI.

[!NOTE] Under UI/GUI I mean strings which are being sent to LSP-client to be displayed in the Clinet's UI at the end.

[owl-from-hogvarts]

Nope, null gets its way to UI at Hover.kt:42.

Instead of returning null, null is being interpolated into a string. I will implement the check for null there and merge your PR.

[owl-from-hogvarts]

Thanks for contribution!

[AlexandrosAlexiou]

Nope, null gets its way to UI at Hover.kt:42.

Instead of returning null, null is being interpolated into a string. I will implement the check for null there and merge your PR.

Thanks!