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 IPython Console, Console and (potentially) other Plugins make (might) use of the collections editor to display env variables and other information.
Since the new API work is decoupling all the moving parts and there will be a precedence in plugin order of loading, this should move out of the variable explorer, as discussed with @ccordoba12
The text was updated successfully, but these errors were encountered:
The IPython Console, Console and (potentially) other Plugins make (might) use of the collections editor to display env variables and other information.
The same goes for the text editor, which is used by the Profiler, Code Analysis and several external plugins.
Plugins will now have optional and required requirements
So it will go something like
internal console
coreui (name to be defined)
ipython console
lsp
editor
The rest...
But since the console was being loaded first, having it depend on the variable explorer did not make much sense. However having all the other plugins depend on the editor does make more sense.
The IPython Console, Console and (potentially) other Plugins make (might) use of the collections editor to display env variables and other information.
Since the new API work is decoupling all the moving parts and there will be a precedence in plugin order of loading, this should move out of the variable explorer, as discussed with @ccordoba12
The text was updated successfully, but these errors were encountered: