You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the ansible language server crawls the file systems and uses a regular expression to extract doc strings from plugins.
In the case of execution environments, having ansible builder extract the doc strings during the build process and store them in the container in a well-known location would allow this to be a one-time process vs. a process that occurred each time the language server was started.
This would limit the interaction between the language server and the EE to a simple file content collection process, eg cat *
Currently the ansible language server crawls the file systems and uses a regular expression to extract doc strings from plugins.
In the case of execution environments, having ansible builder extract the doc strings during the build process and store them in the container in a well-known location would allow this to be a one-time process vs. a process that occurred each time the language server was started.
This would limit the interaction between the language server and the EE to a simple file content collection process, eg cat *
This is the current process the language server uses: https://github.com/ansible/ansible-language-server/blob/707d53c64a29571922a7924cf4e5ff9b6ad4b68e/src/utils/docsParser.ts#L202
The text was updated successfully, but these errors were encountered: