Skip to content

feat: add keyword-not-found project rule (KW05) - #1827

Merged
bhirsz merged 1 commit into
mainfrom
feat/rule-keyword-not-found
Aug 14, 2026
Merged

feat: add keyword-not-found project rule (KW05)#1827
bhirsz merged 1 commit into
mainfrom
feat/rule-keyword-not-found

Conversation

@bhirsz

@bhirsz bhirsz commented Aug 14, 2026

Copy link
Copy Markdown
Member

Adds project rule keyword-not-found (KW05): reports keyword calls that do not match any keyword defined in the file, in the imported resource files or in the imported libraries.

Requires library analysis (--analyze-libraries, enabled by default). To avoid false positives the call is not reported when the available keywords are not fully known:

  • keyword name is built from a variable,
  • any import of the file or of its resources could not be resolved or loaded,
  • library arguments could not be resolved,
  • the file or its resources use Import Library / Import Resource,
  • the library was excluded with --ignored-library.

Stacked on #1826.

@bhirsz
bhirsz marked this pull request as ready for review August 14, 2026 16:43
@bhirsz
bhirsz force-pushed the feat/rule-keyword-not-found branch from 315804f to 02dbfc5 Compare August 14, 2026 16:50
Base automatically changed from feat/rule-ambiguous-keyword-name to main August 14, 2026 16:56
Report keyword calls that do not match any keyword defined in the file, in imported resources or in imported libraries. The rule requires library analysis and skips files whose imports could not be fully resolved.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@bhirsz
bhirsz force-pushed the feat/rule-keyword-not-found branch from 02dbfc5 to 81fd383 Compare August 14, 2026 16:56
@bhirsz
bhirsz merged commit 6d05e1a into main Aug 14, 2026
11 checks passed
@bhirsz
bhirsz deleted the feat/rule-keyword-not-found branch August 14, 2026 17:08
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.

1 participant