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
{{ message }}
This repository has been archived by the owner on Jan 26, 2022. It is now read-only.
Should the close command be removed, so the sidebar is always created and never closed?
While looking at #290, it started to feel a bit confusing to close the debugger sidebar while debugging. That also means users have to keep a mental model that consist of different states:
the debugger sidebar is open / closed
the toggle button is on / off
Removing the possibility to close the sidebar would simplify things greatly. There is only one way to turn on debugging and that is by switching the button on in a notebook, console or file.
For the users who have installed the extension but don't want to use it anymore, they could disable it from the extension manager and that would remove the sidebar.
The text was updated successfully, but these errors were encountered:
Should the
close
command be removed, so the sidebar is always created and never closed?While looking at #290, it started to feel a bit confusing to close the debugger sidebar while debugging. That also means users have to keep a mental model that consist of different states:
Removing the possibility to close the sidebar would simplify things greatly. There is only one way to turn on debugging and that is by switching the button on in a notebook, console or file.
For the users who have installed the extension but don't want to use it anymore, they could disable it from the extension manager and that would remove the sidebar.
The text was updated successfully, but these errors were encountered: