-
Notifications
You must be signed in to change notification settings - Fork 632
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
Robot: no tags for keywords starting with embedded arguments #1570
Comments
masatake
added a commit
to masatake/ctags
that referenced
this issue
Oct 6, 2017
Input: *** Keywords *** ${embedded arg} Starting Single No Operation Oputput: ${embedded arg} Starting Single input.robot /^${embedded arg} Starting Single$/;" k Close universal-ctags#1570. Signed-off-by: Masatake YAMATO <[email protected]>
masatake
added a commit
to masatake/ctags
that referenced
this issue
Oct 6, 2017
Input: *** Keywords *** ${embedded arg} Starting Single No Operation Oputput: ${embedded arg} Starting Single input.robot /^${embedded arg} Starting Single$/;" k Close universal-ctags#1570. Signed-off-by: Masatake YAMATO <[email protected]>
Thank you for reporting. Try #1571. A good test case drives me.
|
masatake
added a commit
to masatake/ctags
that referenced
this issue
Oct 6, 2017
Input: *** Keywords *** ${embedded arg} Starting Single No Operation Output: ${embedded arg} Starting Single input.robot /^${embedded arg} Starting Single$/;" k Close universal-ctags#1570. Signed-off-by: Masatake YAMATO <[email protected]>
I was reading s/old-docs/EXTENDING.html but the changes are more complex than I anticipated. Thanks you very much!! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The keywords in Robot Framework can contain embedded arguments ("variables") in the middle of their definition. And the documentation doesn't seem to restrict their number or position.
But no tags are generated depending on the position of the embedded arguments. Given the following input file,
, these are the tags generated:
Notice no tags are generated for the
*** Starting
keywords.I've attempted to fix it by including an
$
in the first part of the regex for Robot keywords, i.e., changing fromto
Despite that solved the problem for the keywords starting with embedded arguments, the tags for regular variables weren't generated anymore.
I found that unexpected, as the regex for variables doesn't match the keywords starting with embedded arguments, because variables are required to have at least two spaces after the closing braces.
The text was updated successfully, but these errors were encountered: