https://bugs.kde.org/show_bug.cgi?id=456493

--- Comment #6 from nat...@upchur.ch ---
(In reply to Waqar Ahmed from comment #5)
Thanks for your help; I was able to compile and run the branch. 

It took me a little time and reading through your commits to understand that I
needed to go to Project > Code Analysis > Start Analysis to have ESLint run on
my file*. Once I hit Start Analysis, everything seemed to work pretty smoothly,
except that error messages appeared to be duplicated in the Diagnostics output
(see attachment). I noticed live output in the panel from the LSP server, and
ESLint output upon save; line highlighting worked as expected. 

I very much appreciate your work on this; it will really make life easier!


* You don't really benefit much from a full-on IDE for webdev, so some of the
workflows in Kate that (presumably) come from KDevelop have taken some getting
used to for me. It took me ages, for instance, to learn that I could use the
"Build" tool to run an Eleventy / SSG server, but given the way RAM gets eaten
when I do this, I'm not sure whether I ought to be using it this way.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to