-
-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ENHANCEMENT] Python Syntax Highlighting in Robot Framework Files #230
Comments
It is implicitly mentioned in "etc." but it looks like most of the keyword ending by But what about the keywords which are not in BuiltIn? Like for Browser library assertions, or even custom libraries. Could this be implemented?
No "etc." here, so I would like to add that |
@gohierf and @touchedthecode published a new version with support for python syntax in IF and WHILE expressions. Can you please test it and give me a short feedback? I have released a new version with support for Python syntax highlighting in IF and WHILE expressions. Can you please test it and give me some feedback? I'm not sure how to do the highlighting for keywords yet, it might take a while. As a workaround you can also use an inline python expression variable, something like this: *** Test Cases ***
forth
VAR ${a_var} 1
Should Be True ${{ $a_var == '1' }} |
Hei Daniel, nice work! It looks good on my side. I will keep an eye open on the topic, but so far no problem! |
Also, I see that you have fixed the But it was nice when all five characters of Sorry to be picky, I hope it reads as constructive feedback. |
I cannot really do this, because that's depending of VSCode |
Is your enhancement request related to a problem? Please describe.
The absence of syntax highlighting for Python statements in Robot Framework files hinders code readability and increases the likelihood of errors.
Describe the solution you'd like
Integrate syntax highlighting for Python statements in Robot files, using a distinctive color scheme to enhance visibility and comprehension.
${{}}
expressionsNote
Partially related to #229
The text was updated successfully, but these errors were encountered: