Contributing a text editor provider raises warning, even when user selects it as 'workbench.editor.defaultBinaryEditor'
#230.179 aberto em 30 de set. de 2024
Métricas do repositório
- Stars
- (74.848 stars)
- Métricas de merge de PR
- (Mesclagem média 11h 43m) (1.000 fundiu PRs em 30d)
Description
Contributing a 'CustomTextEditorProvider', to be selected by the user as 'workbench.editor.defaultBinaryEditor' still raises the warning of 'File seems to be binary and cannot be opened as text'
Context: We are currently developing a VSCode extension, to parse binaries with objdump and provide the information about the binary. We need the output to be presented in a text editor, not a custom editor as we are contributing a new language model for objdump output. So, mainly we need the output syntax coloring, as document symbols to be provided, which is not possible in the custom editor WebView.
We need a way to bypass the warning, as the user selects the provided custom text editor as the default binary editor.