-
Notifications
You must be signed in to change notification settings - Fork 112
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
Paths and import of libraries #22
Comments
Hello, thank you very much for your kind words! As to your remarks:
Hope this clarifies your doubts; feel free to ask further if you find something more, we will be happy to help and assist! Cheers, |
Hello Michal! Thank you a lot for your reply and sorry for the delay with a reply. I was trying out all you mentioned here :) So lets go to the points:
The only thing that didnt work for me was the 'Automatically discover and add libraries to red.xml'. When I performed what you mentioned, a new screen pops up, but no library was found. Do you know what that might be?
and I have a pythonpath variable pointing to the site-packages folder. thank you for everything one more time! Cheers, |
Hi,
to clarify: once you've disabled automatic build and did simple clean without building the project again, the files are rather "not validated", than "green"
This is relatively new feature, but it should work quite right already. In essence it looks through all the files in your project (when run on project) for library imports and tries to locate them. In order to make it work properly the library should be located either somewhere in your project or in PYTHONPATH (either in system, or added in red.xml). If the test with this library import runs correctly then it should also be discovered in most cases. Is it possible for you to prepare some tiny example which does not work? A project with suite which imports the library and this library cannot be discovered should be sufficient.
it seems that you wanted to add some paragraph here, but it's missing. Cheers, |
@rpwerner: Any feedback? |
Hello, Unfortunately I had some realocations and I couldn't work on the plugin for our project anymore. Fornow I wasn't able to do the small example. But all the other hints were very welcome and I distributed to other developers and they work as expected for them as well. Cheers, |
Hi, I followed the above and get the library recognized in my resource file. Now there is no red line over the specified library. But when calling a java method as keyword for the same library, it errors as "unknown keyword 'givenmethodnamed' ". Please help me overcome this issue. |
Hi, In order to see keywords from libraries RED has to generate library specification file (using robot.libdoc tool provided with Robot). To do it in your project you have to:
After project is built and validated you should see keywords in content assist of editor (Ctrl+Space) as well as there should be no errors reported on those keywords. |
Hi Team , •Path '../../CommonFiles/CommonUpointKeywords.resource' points to location outside your workspace |
Hello
Amazing plugin! thank you very much! I didnt use too much yet, but the fact that I can debug through the keywords is already something.
While using and configuring a project, some points came up and I would like to know if you could clarify to me:
When I include a path into red.xml to a referenced library, I got a warning saying that it would be better to put a relative path to it and I actually wanted to do that.
But I couldnt find or figure out how to do it. I saw in one of the images on the documentation and it was something like "folder/file.py" and I tried editing the red.yml myself, but it didnt recognize. Is there a way to use relative paths?
I have several robot files on my project and all of them are "red" with unknown keyword error or unknown library. Once I open one of them, configure the correct library for that file in red.xml, everything works fine. Then I open a second file, which also has the same libraries that the first file had, but the keywords or libraries were again "red". I thought that if I fix once for a library, it would apply to all robot files that are using that library. Have you seen this problem? Is there a way to have the configuration once set and applies to all files?
Once I realized the Errors when the Robot project is imported as General->File System (eclipse symlink) #2 issue, I tried to run the test case without fixing the import of libraries and for my surprise the test was executed successfully. Is this something that you are aware?
Thank you in advance.
Cheers,
Rafael
The text was updated successfully, but these errors were encountered: