DAP has a notion of "loaded sources" which allows the debugee to provide data that the frontend can display. For example, the original display of the parse data (hex view) and infoset used this. However, the extension itself manages now manages these views via custom DAP requests, so the sources capability should be disabled in the backend.
This will remove the "Loaded Scripts" view the left-hand pane, but all other functionality will remain the same. (Interacting with this pane brings up the backend-provided data and infoset views, which is confusing since we have the extension managing the views.)
DAP has a notion of "loaded sources" which allows the debugee to provide data that the frontend can display. For example, the original display of the parse data (hex view) and infoset used this. However, the extension itself manages now manages these views via custom DAP requests, so the sources capability should be disabled in the backend.
This will remove the "Loaded Scripts" view the left-hand pane, but all other functionality will remain the same. (Interacting with this pane brings up the backend-provided data and infoset views, which is confusing since we have the extension managing the views.)