Embedded keywords with variable are treated as not capitalised
See original GitHub issueDescribe the bug Embedded keywords with variable are treated as not capitalised, while IMHO they are fine formatted.
To Reproduce Run robocop against file containing following code
*** Variables ***
${variable} does not matter
*** Test Cases ***
Test Capitalised
Embedded Keyword With ${variable}
*** Keywords ***
Embedded Keyword With ${variable}
Log ${variable}
Results in [W] 0302 Keyword name should be capitalized message form Robocop
Expected behavior Since common approach to variables is to have them lowercased or uppercase, for global variables/Constans, rule should ignore embedded variable casing.
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (7 by maintainers)
Top Results From Across the Web
Why should I capitalize my SQL keywords? Is there a good ...
I personally find a string of lowercase characters to be more readable than a string of uppercase characters.
Read more >Capitalization Rules - Wiki
Initial letters capitalized and words run together (like PascalCase), but each capital letter must be followed by a lower case letter (hence one-letter...
Read more >Capital Offense: How to Handle Abbreviations in CamelCase
The only convention that works reliably is this: “Treat abbreviations just like ordinary words”. That is, don't use all-capital letters:.
Read more >Recommended C Style and Coding Standards
This document is an updated version of the Indian Hill C Style and Coding Standards paper, with modifications by the last three authors....
Read more >The Go Programming Language Specification
Identifiers name program entities such as variables and types. ... The following keywords are reserved and may not be used as identifiers.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Let’s keep it open for now because reading the context is on our roadmap - although I agree it’s a lot of work (but I hope to steal some knowledge from other open source tools that are dealing with keyword definition information 😉)
Closing it since we decided some time ago that we will not implement context reading. Such feature can be requested from our friends from https://github.com/robocorp/robotframework-lsp 😉