LSP 0.6.0: No rpaframework keywords found when using rpaframework greater than 6.4.*
See original GitHub issueLSP 0.6.0 (VS Code) complains about missing keywords when using rpaframework greater than 6.4.* (so 6.5.*, 6.6.*, 6.7.*).
- Built-in keywords are found (only
rpaframeworkseems to be affected). - Running the robot works (only LSP seems to be affected).
Can be replicated with this simple robot, where Absolute Path is either found or not based on the rpaframework version. This affects possibly other rpaframework libraries, too:
*** Settings ***
Library RPA.FileSystem
*** Tasks ***
File system operations
${absolute_path}= Absolute Path ${CURDIR}
This is potentially an issue with
rpaframeworkitself, but since it only seems to affect LSP, posting here.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6
Top Results From Across the Web
Release notes — RPA Framework documentation
Provides the following generic keywords capable of working with all the engines above: Init Engine. Switch Engine. Predict.
Read more >VSCode new Create Robot Project can't find Python Keywords
I used “Robocorp: Create Robot”, used the Extended template and without changing any configuration “Robocorp: Run Robot” worked fine!
Read more >rpaframework - PyPI
We are looking at improving our keyword usage to cover situations where developer might be struggling to smoothly write task for a Robot....
Read more >所有selenium相关的库- 始識 - 博客园
库简介:ctreport-selenium is a simple, creative and a customizable report for automation testing using Python. Best suitable for pytest, ...
Read more >Interesting keywords from RPA Framework libraries (release ...
Specifically Run Macro to run macros by name in .xlsm files. RPA.Excel.Files Interfacing Excel files without opening an application (which is ...
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

Yeap, I’ll add the fallback anyways.
As for the dep being on RF itself, I’m still uncertain… it really does make sense to add that dep only for libraries that actually rely on reST (and thus, being only an optional dep for RF).
Alright, makes sense about environments. I can add docutils to rpaframework dependencies as a fix, but I want to make clear that the error comes from RF’s libdoc and it advertises first-class support for reST docstrings. There will be other libraries with similar issues, and bad docstrings would probably be better than no autocomplete for them at all.