--config flag is broken

[irmiller22]

Hi! It seems like the latest release broke the way the --config flag is handled?

I use the --config flag in my CI/CD workflow for markdown linting, and as of a few hours ago it's no longer respecting the configuration that I've set up.

UPDATE:

Adding additional context with an example:

# .github/markdownlint.yaml

MD007:
  indent: 4
MD013: false
MD040: false
MD046: false

markdownlint -c .github/markdownlint.yaml .

The settings specified in .github/markdownlint.yaml were being respected until a few hours ago, which I imagine coincides with the 0.27.0 release.

[DavidAnson]

See also DavidAnson/markdownlint#373

I'll have a look tonight.

[DavidAnson]

Can you please give an example that does not work? All the tests are passing, so it should not be completely broken?

[irmiller22]

Sure, I'll also add it to the initial comment:

# .github/markdownlint.yaml

MD007:
  indent: 4
MD013: false
MD040: false
MD046: false

markdownlint -c .github/markdownlint.yaml .

The settings specified in .github/markdownlint.yaml were being respected until a few hours ago, which I imagine coincides with the 0.27.0 release.

[DavidAnson]

Thanks, I can reproduce this. Looking now...

[DavidAnson]

I should have a fix shortly.

[DavidAnson]

Please try `v0.27.1', thanks, and sorry for the trouble!

[irmiller22]

@DavidAnson no worries, thank you for the fix!