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
The Notebook API is blocking some modern python plug-ins from being compatible with Theia, as well as Jupyter notebooks. This blocks off the AI/ML crowd from using Theia. A stop-gap solution would be to stub out the APIs at first and see which ones need fixing next.
The text was updated successfully, but these errors were encountered:
Right, stubbing out certain API to make extensions at least work with the other API that is fully supported would certainly help in many cases. However, if something is just stubbed, I think we should make very clear that it isn't "functionally" supported.
I would maybe suggest to enhance the vscode-theia-comparator info.yml, allowing to mark namespaces/types specifically as stubbed, so that they show up as warning (orange), meaning that the types are available but actually not functional. WDYT?
Bug Description:
The Notebook API is blocking some modern python plug-ins from being compatible with Theia, as well as Jupyter notebooks. This blocks off the AI/ML crowd from using Theia. A stop-gap solution would be to stub out the APIs at first and see which ones need fixing next.
The text was updated successfully, but these errors were encountered: