Hi, @idanpa and thank you for the extension!
So, long story short, I need this to have some additional features:
- support log parsing when there
--showfile
option is passed to the checkpatch
- support a possibility to define a particular cwd for multiroot workspaces to make checkpatch use a config from specific workspace
I'm not a person who familiar with js, ts or vscode-extensions creation. But I can provide a pull-request where I'll try to do my best to implement these features. It may violate typical codestyle or common sense for ts, though.
Now, some details.
The idea behind the first feature is to implement an alternative parseCheckpatchLog()
function (or addition to it) which may handle a different output from checkpatch. For comparison:
WARNING:LINUX_VERSION_CODE: LINUX_VERSION_CODE should be avoided, code should be for the version to which it is merged
#124: FILE: mac.c:124:
+#if KERNEL_VERSION(5, 8, 1) <= LINUX_VERSION_CODE
- this style of logs is supported for now.
mac.c:124: WARNING:LINUX_VERSION_CODE: LINUX_VERSION_CODE should be avoided, code should be for the version to which it is merged
+#if KERNEL_VERSION(5, 8, 1) <= LINUX_VERSION_CODE
- This style I want to be supported (here --showfile
option was passed to checkpatch).
About second feature. I think it would be good to define some option that a user can define inside settings.json
of a particular workspace, and then extension should use this workspace as cwd, but not the root. I don't know if this possible or some other approach should be choosen. Of course this related to the Checkpatch Selected File
feature.
I need some feedback for it from you,
Cheers.