[kate] [Bug 456493] Feature Request: ESLint

2023-01-21 Thread Waqar Ahmed
https://bugs.kde.org/show_bug.cgi?id=456493 --- Comment #17 from Waqar Ahmed --- > 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 confi

[kate] [Bug 456493] Feature Request: ESLint

2023-01-11 Thread Waqar Ahmed
https://bugs.kde.org/show_bug.cgi?id=456493 --- Comment #14 from Waqar Ahmed --- Git commit 7085c17e6a77a12cf16055d9e21ac5f5c6c40895 by Waqar Ahmed. Committed on 11/01/2023 at 17:13. Pushed by waqar into branch 'master'. Add Eslint tool Basic support. You can run the tool manually. In a follow

[kate] [Bug 456493] Feature Request: ESLint

2023-01-11 Thread Waqar Ahmed
https://bugs.kde.org/show_bug.cgi?id=456493 Waqar Ahmed changed: What|Removed |Added Latest Commit|https://invent.kde.org/util |https://invent.kde.org/util |it

[kate] [Bug 456493] Feature Request: ESLint

2023-01-11 Thread Waqar Ahmed
https://bugs.kde.org/show_bug.cgi?id=456493 Waqar Ahmed changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit|

[kate] [Bug 456493] Feature Request: ESLint

2023-01-10 Thread bugzilla_noreply
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 p

[kate] [Bug 456493] Feature Request: ESLint

2023-01-09 Thread Waqar Ahmed
https://bugs.kde.org/show_bug.cgi?id=456493 --- Comment #12 from Waqar Ahmed --- > I still have the same issues when running from Code Analysis Right. I forgot to push the change for that. Exit Code 0 wasn't being considered as a success code so it was erroring out. Should work now I think. Besi

[kate] [Bug 456493] Feature Request: ESLint

2023-01-09 Thread bugzilla_noreply
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

[kate] [Bug 456493] Feature Request: ESLint

2023-01-08 Thread Waqar Ahmed
https://bugs.kde.org/show_bug.cgi?id=456493 --- Comment #10 from Waqar Ahmed --- I think all these problems should be fixed now. > many users wouldn't think to enable the projects plugin, especially for > simple web projects That is okay, but I would still recommend enabling it always as a lot

[kate] [Bug 456493] Feature Request: ESLint

2023-01-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=456493 --- Comment #9 from nat...@upchur.ch --- (In reply to Waqar Ahmed from comment #8) > I have removed "Eslint current file" from the "Code Analysis" tab and > replaced it with "ESLint" which will run on the whole project instead of > just the current file.

[kate] [Bug 456493] Feature Request: ESLint

2023-01-08 Thread Waqar Ahmed
https://bugs.kde.org/show_bug.cgi?id=456493 --- Comment #8 from Waqar Ahmed --- Thanks for the feedback, it helped find a critical issue. I have removed "Eslint current file" from the "Code Analysis" tab and replaced it with "ESLint" which will run on the whole project instead of just the curren

[kate] [Bug 456493] Feature Request: ESLint

2023-01-07 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=456493 --- Comment #7 from nat...@upchur.ch --- Created attachment 155100 --> https://bugs.kde.org/attachment.cgi?id=155100&action=edit ESLint Error Duplication in Diagnostics Output -- You are receiving this mail because: You are watching all bug changes.

[kate] [Bug 456493] Feature Request: ESLint

2023-01-07 Thread bugzilla_noreply
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 >

[kate] [Bug 456493] Feature Request: ESLint

2023-01-07 Thread Waqar Ahmed
https://bugs.kde.org/show_bug.cgi?id=456493 --- Comment #5 from Waqar Ahmed --- Switch to the folder which contains Kate source code. Then run git fetch It will fetch all branches. Then switch to the branch in the merge request you want to test git checkout work/diagnostics Then run kdesrc-bu

[kate] [Bug 456493] Feature Request: ESLint

2023-01-06 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=456493 --- Comment #4 from nat...@upchur.ch --- (In reply to Waqar Ahmed from comment #3) > An MR is already in review which includes basic ESLint integeration. It > would be great if you could test :) > > https://invent.kde.org/utilities/kate/-/merge_requests

[kate] [Bug 456493] Feature Request: ESLint

2023-01-03 Thread Waqar Ahmed
https://bugs.kde.org/show_bug.cgi?id=456493 --- Comment #3 from Waqar Ahmed --- An MR is already in review which includes basic ESLint integeration. It would be great if you could test :) https://invent.kde.org/utilities/kate/-/merge_requests/1051 -- You are receiving this mail because: You ar

[kate] [Bug 456493] Feature Request: ESLint

2023-01-03 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=456493 --- Comment #2 from nat...@upchur.ch --- (In reply to Waqar Ahmed from comment #1) > If someone is up for it, this should be easy to implement. I wish I even knew where to begin; I think this would be a very useful feature to a lot of people. -- You a

[kate] [Bug 456493] Feature Request: ESLint

2022-07-21 Thread Waqar Ahmed
https://bugs.kde.org/show_bug.cgi?id=456493 Waqar Ahmed changed: What|Removed |Added CC||waqar@gmail.com --- Comment #1 from Waqar Ahm