https://bugs.kde.org/show_bug.cgi?id=456493
--- Comment #13 from nat...@upchur.ch --- (In reply to Waqar Ahmed from comment #12) > Exit Code 0 wasn't being considered as a success code so it > was erroring out. Should work now I think. Yep! This is no longer occurring. Running from the Project panel still doesn't output ESLint errors for test2.js though, only test.js. > There is still the issue that if there is no eslintrc file or eslint is not > initalized for a project, it will error out. I really like the idea of a fallback config in future (and maybe even an interface to customize it in the plugin settings); maybe a simple error message would be helpful for now? Something like "No ESLint configuration found. Ensure that ESLint is installed and initialized. See (URL) for more information. Speaking of ideas for the future: it would be amazing to be able to have it work live; generating error messages without needing to save. If you want, and the MR is accepted, I could help write user documentation on the plugin for The Kate Handbook? -- You are receiving this mail because: You are watching all bug changes.
