Closed bgd77 closed 11 years ago
Regarding loading a resource file using variables; I think the implementation does not yet support ${RESOURCES} in paths.
Regarding the the keyword being prefixed with the library name - does the referenced resource file happen to (directly or indirectly) load the same library? In that case the unnecessary prefixing (and possibly also the main problem in this issue) might be related to or duplicate of #35..
Indeed, it happens only when both the resource file and the scenario import the same library. So this is a duplicate of issue 35. I think it can be closed.
Closed as duplicate of #35.
Opened new issue #40 for the Resource ${RESOURCE}/file.txt
case.
Included in release 1.1.0.
According to Robot Framework documentation, for "Python libraries in modules or Java libraries in packages, the full name including the module or package name must be used." (see http://robotframework.googlecode.com/hg/doc/userguide/RobotFrameworkUserGuide.html?r=2.7.5#using-library-setting)
For example: Library com.company.TestLib
As a consequence the name of the index file would be "com.company.TestLib.index". In this case, when using the content assistance (Ctrl + Space), the keywords from the index files are shown twice.
Also, when one keyword is selected, the name of the library is displayed before the name of the keyword. For example, for keyword "Save" from the above library, the following is inserted in the test file: "com.company.TestLib.Save" It should be only "Save".
NOTE: This only happens when there is a resource declared with relative path after the library declaration. E.g. Resource ../../../resource/file.txt
If a variable is used for resource, the issue described above is not present E.g. Resource ${RESOURCES}/file.txt