[dmt] update copyright year and add no_lang_key tests#365
Merged
Conversation
Signed-off-by: Ruslan Gorbunov <ruslan.gorbunov@flant.com>
fuldaxxx
changed the title
ldmonster
approved these changes
May 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Unit tests for the no-lang-key documentation linter rule (pkg/linters/docs/rules/no_lang_key.go). Covers front matter parsing, lang: key detection with line number reporting, integration
through CheckFiles with mock modules, exclude rules, edge cases (empty path, subdirectories, non-md files).
Why do we need it, and what problem does it solve?
The no-lang-key rule was added without test coverage. Without tests, any future refactoring of front matter parsing or lang: key detection logic could silently introduce regressions - for example, false positives on language: keys, missed detection when lang: appears with tabs instead of spaces, or incorrect behavior when lang: is present in the document body outside
front matter.