https://bugs.kde.org/show_bug.cgi?id=456493
--- Comment #11 from nat...@upchur.ch --- (In reply to Waqar Ahmed from comment #10) > I would still recommend enabling it always as a lot of > kate stuff works better if there is a project around Yea, I do find myself making use of it lately. I like the notes. > By auto-fix I mean for some diagnostics a source can provide a "fix". From > the cmd line you would do eslint --fix, and it would fix stuff for you. Tested this - love it. I had no idea such a thing existed. All issues with the ESLint plugin look resolved for me, but I still have the same issues when running from Code Analysis. Maybe It's the way I set up the project? I just used "Open Folder" to open a directory containing two .js files; there's no git repo or project file like there would be in KDevelop. Do I need one of these things for it to function correctly? -- You are receiving this mail because: You are watching all bug changes.
