v8r configuration file not working?

[bdovaz]

This page describes how to create a configuration file for this linter: https://github.com/chris48s/v8r#configuration

In my case, I want to customize several schemas because in the repository there are several azure-pipelines*.yml or docker-compose*.yml files that not having the standard name, it does not take the schema and I want to indicate it.

When running megalinter it seems that it is as if this file does not exist.

[Kurt-von-Laven]

Usually, I would suggest adding YAML_V8R_CONFIG_FILE: LINTER_DEFAULT to your MegaLinter config, but the setting doesn’t appear to exist. Feel free to open a pull request to add this setting.

[bdovaz]

I have added the field in the descriptor, as I don't quite understand the whole flow in megalinter descriptors, seeing the link in my first post and how the configuration file resolution works in this linter, do you think something else is needed?

[nvuillam]

@bdovaz config_file_name will make that cli_config_arg_name will be used if the file is found in

• root folder of the repo
• .github/linters
• TEMPLATES (default config in megalinter)

cli_config_arg_name is -c by default, does v8r understand this arg ?

[bdovaz]

@nvuillam According to this link: https://github.com/chris48s/v8r#configuration

It says that you don't need to pass any parameter and that it automatically looks for it in the working directory under the listed names and by default I have chosen ".v8rrc.yml" but that's why I don't understand what to do in this PR. This linter supposedly does not need to pass any parameter, it simply looks for files with those names in the working directory and that is what does not work with megalinter and it does if I run the linter outside on my own with the npm package, for example: v8r filetocheck.yml

[nvuillam]

The problem is that the list of files is sent in absolute format, cwd is not the root of the repo.
I have a PR pending but there is still some bug so I can't merge it yet :/

[bdovaz]

Ok, I'll wait then, can you mention here which one it is? To have it tracked

[nvuillam]

@bdovaz this one
#1877

If you find why there is some strange stuff provoking timeout.... you're a MegaLinter hero ! :D ( I'm very busy at my actual job these days, I unfortunately have less time for open source :/ )

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity.
It will be closed in 14 days if no further activity occurs.
Thank you for your contributions.

If you think this issue should stay open, please remove the O: stale 🤖 label or comment on the issue.

[bdovaz]

Any news?

[nvuillam]

We still need to make pass the PR that uses relative paths :/

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity.
It will be closed in 14 days if no further activity occurs.
Thank you for your contributions.

If you think this issue should stay open, please remove the O: stale 🤖 label or comment on the issue.

[bdovaz]

No stale, waiting for #1877

[bdovaz]

It has been resolved long ago.