priv-kweihmann / oelint-vscode Goto Github PK

Needs to use backticks to enable template strings:

    for (var opt of config.get("oelint-vscode.run.constmodadd")) {
        res.push(`--constantmods=+${opt}`);
    }
    for (var opt of config.get("oelint-vscode.run.constmodrem")) {
        res.push(`--constantmods=-${opt}`);
    }
    for (var opt of config.get("oelint-vscode.run.constmodovr")) {
        res.push(`--constantmods=${opt}`);
    }

Make the linter run from the given workspace dir, so it could automatically find the recently introduced user configuration from that path

#4 adds a few options that are missing in the README - add them

I am using the oelint-adv and the vscode plugin since end 2023 during reviews of different yocto recipes. The plugin stopped to work after an update of vs-code, to V1.88.1 . I assume the issue is caused from the vscode extension "BitBake language support" which is marked as deprecated in that version.

Can someone check it and give me recommendation how to fix it?

Best Regards

Steffen

Latest oelint added additional options, add them to the addin

Like

• suppression
• additional non standard rules
• additional rule directories
• fix (+ nobackup switch)

Add options for the lately introduced --constantmod CLI switch

On startup the tool shall auto-update/auto-install the tool.
Maybe introduce a config variable to control the behavior

Current update check does pip3 install --user --upgrade ... which is a problem when the user is root, as it's likely that root doesn't have the necessary directories (like home) setup - this for instance can be seen in some docker containers.
So to enable these use cases make the --user argument in the call configurable

I suspect a similar changes as in priv-kweihmann/meta-sca#1163 needs to be applied