-
Notifications
You must be signed in to change notification settings - Fork 12
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 IntelliSense with ontology information #591
Comments
I started to work on this in the linked pull request, but later I realized that it is only possible to solve this issue in a simple way when the user is working with IPython. When using IPython (i.e. Jupyter notebooks), some times the user will be coding when the namespace has been already imported. Therefore, the However, when using an IDE such as VSCode or Pycharm, the story is different. The IDE does not run the code and keep a Python kernel with the result, so it cannot use the There is however a hacky "solution", which I do not like too much, but maybe @yoavnash, which is a user of OSP-core and I think needs this feature can give better input on this. There exist Python type hinting stub files ( The trick is, that in this file you can specify types for things that do not actually exist in the It is up to the IDE to support those Since these stub files do not need to be included in the same package as the python files themselves, I though that OSP-core could generate a Do you think this would bring the intended benefit and is worth implementing? Did any better idea come to your mind? Should we just accept that this is too hacky and close the issue? |
I think it might relate to this? |
Exactly, this person wants the same functionality as us. |
It would be a nice feature to get autocompletion and argument information when instantiating objects from the ontology classes.
For example, the code:
Should suggest the autocompletion to
Wrapper
, and inform that it requires asession
parameter.I am not sure how easy, or even if it is possible, but I think it is definitely worth looking into at some point.
Things that should be implemented:
The text was updated successfully, but these errors were encountered: