Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong interpretation of the configuration file #211

Open
BnGx opened this issue Oct 25, 2023 · 1 comment
Open

Wrong interpretation of the configuration file #211

BnGx opened this issue Oct 25, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@BnGx
Copy link

BnGx commented Oct 25, 2023

1️⃣ Description

The program yamlfixer does not evaluate the .yamllint configuration file in the same way as yamllint.

📑 Steps to Reproduce

  • Create a .yamllint configuration file and set the ignore option with a glob to ignore;
  • Run yamlfixer against an ignored yaml file.

2️⃣ Expected behavior

The interpretation of the configuration file should be the same between yamlint and yamlfixer.

3️⃣ Scripts

mkdir mydir
echo "no_document_start: yes" > mydir/myfile.yaml
echo "ignore: [mydir/myfile.yaml]" > .yamllint
yamlfixer mydir/

ℹ️ Environment details

  • OS: Ubuntu 22.04
  • Python runtime: 3.10
  • Yamlfixer version: 0.9.15
  • Used shell: bash
@BnGx BnGx added the bug Something isn't working label Oct 25, 2023
@BnGx BnGx changed the title Bug report Wrong interpretation of the configuration file Oct 25, 2023
@tamere-allo-peter
Copy link
Member

Thanks @BnGx for your report. Currently yamlfixer doesn't read yamlint's configuration file, that's why you are experiencing this problem. No time to work on yamlfixer for now, sorry.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants