-
Notifications
You must be signed in to change notification settings - Fork 35
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
Support Robot's libdoc xml format when defining 3rd party libraries #48
Comments
@Tattoo |
I am adding the generated json file inside library-docs however when I type the library name vscode says:
Is there any suggestion on how to solve this issue? |
It might be a bit hacky. But i don't like to add all keyword to my settings for several reasons. Instead of adding all kw to settings (
I rather simply like todo
To make this working, I used the nice helper tool from @Snooz82 (robotframework-LibDoc2Json) as follows:
Anyhow, this is a simple workaround with the given tools. Let the extention work with the xml output of libdoc (or maybe trigger robot.libdoc to generate an xml from third party libs) would do the trick much more clean 👍 |
Generally with Robot Framework, one ends up with writing a lot of small libraries as well as employing the wealth of existing libraries in the ecosystem (see External tab)
Currently, Intellisense to be able to find keywords from 3rd party libraries by defining them keyword-by-keyword under
rfLanguageServer.libraries
setting.Robot Framework has built-in documentation tool
libdoc
that 3rd party library developers are expected to use to document their libraries. This tool supports outputting library's keyword documentation in XML format, intended for editors and similar tools to have easily programmatically readable format. Users can also create these XML specs themselves as well from any library they might have.It would be great, if I could simply define paths to the xmls I already have, something akin to this:
The text was updated successfully, but these errors were encountered: