fix(yfmlint): keep error level after double normalization #5243

[kadymov]

Description

The basic logic and fixes are here: diplodoc-platform/yfmlint#73

Problem

fixes #5243

Standard markdownlint rules (MD010, MD018, etc.) configured as error in .yfmlint were silently downgraded to warn. As a result, the build kept passing when it should have failed — the violations were only written to the log at WARN level.

Root cause

The lint config is normalized twice by two independent layers:

1. CLI — the Lint feature expands the log-levels section, merges it with the config, and calls normalizeConfig (needed to support log-levels and to append MD033).
2. yfmlint package — being a self-contained library, it calls normalizeConfig again when merging with its default config.

normalizeConfig was not idempotent: when processing the object form of a rule, the level was read only from the .level field. An already-normalized object {loglevel: 'error'} has no .level, so the fallback to the default warn kicked in and the original error was lost.

Fix

Added a fallback to the already-present loglevel field in the object-normalization branch:

loglevel: objectConfig.level || objectConfig.loglevel || DEFAULT_LOG_LEVEL

Re-running normalization on an already-normalized config now yields the same result, and the error level is preserved. Neither of the two normalizeConfig calls had to be removed — both are required for the respective layers to work correctly.

Related issue: #5243

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud