Skip to content

feat(#566): add invalid-name-notation lint - #1235

Open
VasilevNStas wants to merge 3 commits into
objectionary:masterfrom
VasilevNStas:fix/issue-566-invalid-name-notation
Open

feat(#566): add invalid-name-notation lint#1235
VasilevNStas wants to merge 3 commits into
objectionary:masterfrom
VasilevNStas:fix/issue-566-invalid-name-notation

Conversation

@VasilevNStas

Copy link
Copy Markdown
Contributor

fix #566

New lint invalid-name-notation checks that every @name in the XMIR matches [a-z]+(-[a-z]+)* — kebab-case, Latin letters only, no digits/underscores/uppercase, as requested in #566.

  • src/main/resources/org/eolang/lints/names/invalid-name-notation.xsl — the lint (warning severity, same defect shape as non-kebab-name).
  • src/main/resources/org/eolang/motives/names/invalid-name-notation.md — motive.
  • eo:special now also recognizes ξ (xi), an internal parser symbol alongside φ/λ; otherwise parser-generated <o name="ξ"/> inside atoms would be flagged.
  • 4 YAML packs: allows-good-names, allows-special-names (incl. φ, λ, a🌵N-N auto-names and test names), allows-throwing-test-name, catches-invalid-names.
  • canonical.eo: renamed the [i1] lambda parameter to [i] in canonical.eo — digits are now forbidden by design (confirmed by @yegor256 in invalid-name-notation Lint for @name Attribute Matching Not Created #566).

Verified: mvn clean install -Pqulice green (404 LtByXslTest + all suites), mvn jmh:benchmark passed.

@VasilevNStas

Copy link
Copy Markdown
Contributor Author

@yegor256 @volodya-lombrozo plz review

Comment thread src/test/resources/org/eolang/lints/canonical.eo
Comment thread src/main/resources/org/eolang/funcs/special-name.xsl
Comment thread src/main/resources/org/eolang/funcs/special-name.xsl

@volodya-lombrozo volodya-lombrozo left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@VasilevNStas Thank you for the contribution! Could you clarify the questions below, please?

@VasilevNStas
VasilevNStas force-pushed the fix/issue-566-invalid-name-notation branch 3 times, most recently from 11d7982 to 550e172 Compare August 16, 2026 12:56
@VasilevNStas
VasilevNStas force-pushed the fix/issue-566-invalid-name-notation branch from 550e172 to 9f51cec Compare August 16, 2026 13:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

invalid-name-notation Lint for @name Attribute Matching Not Created

2 participants