jiebi/CodeConvo huggingface dataset:
Change:
import { ITerminalCommand, TerminalCapability } from 'vs/workbench/contrib/terminal/common/capabilities/capabilities'; import { TerminalCapabilityStoreMultiplexer } from 'vs/workbench/contrib/terminal/common/capabilities/terminalCapabilityStore'; import { IEnvironmentVariableInfo } from 'vs/workbench/contrib/terminal/common/environmentVariable'; <del> import { getCommandHistory } from 'vs/workbench/contrib/terminal/common/history'; </del> <ins> import { getCommandHistory, getDirectoryHistory } from 'vs/workbench/contrib/terminal/common/history'; </ins> import { DEFAULT_COMMANDS_TO_SKIP_SHELL, INavigationMode, ITerminalBackend, ITerminalProcessManager, ITerminalProfileResolverService, ProcessState, ShellIntegrationExitCode, TerminalCommandId, TERMINAL_CREATION_COMMANDS, TERMINAL_VIEW_ID } from 'vs/workbench/contrib/terminal/common/terminal'; import { TerminalContextKeys } from 'vs/workbench/contrib/terminal/common/terminalContextKey'; import { formatMessageForTerminal } from 'vs/workbench/contrib/terminal/common/terminalStrings';

Discussion:
We should not sync this Should this be per terminal instance? No We should persist similar to recent commands as well Should persisted entries work across different shells? Probably We should invalidate entries similar to commands Let's support removing entries, using a icon that shows only on active and hovered item Let's not use the x for failed, we can improve visualizing errors later on
Change:
public flip(): RangeMapping { return new RangeMapping(this.modifiedRange, this.originalRange); } <ins> /** * Creates a single text edit that describes the change from the original to the modified text. */ public toTextEdit(modified: AbstractText): SingleTextEdit { const newText = modified.getValueOfRange(this.modifiedRange); return new SingleTextEdit(this.originalRange, newText); } </ins> }

Discussion:
Type: <bBug</bStep 1: Create a file named with this content: Step 2: create an empty file named Step 3: Move with a terminal in the folder containing the files and run Step 4: Click on the arrow button and see that it doesn't work ! VS Code version: Code 1.88.1 (, 2024-04-10T17:41:02.734Z) OS version: WindowsNT x64 10.0. Modes: <details<summarySystem Info</summary </details<details<summaryExtensions (38)</summaryExtensionVersion ------ vscode-nginx-conf0.3.5 swagger-viewer3.1.2 freezed0.9.6 ccs-flutter-color1.2.4 dart-code3.86.0 flutter3.86.0 jquerysnippets0.0.1 es7-react-js-snippets4.4.3 vscode-html-css2.0.9 copilot1.180.0 copilot-chat0.14.1 vscode-github-actions0.26.2 vscode-pull-request-github0.86.1 gc-excelviewer4.2.59 todo-tree0.0.226 vscode-nginx-conf-hint0.3.1 latex-workshop9.20.0 vscode-edit-csv0.9.1 plantuml2.18.1 vscode-peacock4.2.2 dotenv1.0.1 vscode-docker1.29.0 debugpy2024.5. isort2023.13. python2024.5. vscode-pylance2024.4.102 remote-containers0.354.0 cpptools1.19.9 vscode-thunder-client2.21.11 nginx-formatter0.0.13 vscode-xml0.26.1 vscode-yaml1.14.0 scala0.5.7 markdown-preview-enhanced0.8.13 even-better-toml0.19.2 vscode-icons12.7.0 vscode-nginx0.7.2 txt-syntax0.2.2 </details
working on this
Oh wow I did not realize this was fixed. I've been working on it and just submitted a PR for a similar issue.
My solution was also very similar.
sorry! It was tricky to fix though.
Change:
event.stopPropagation(); } }); <ins> this._register($(window).on(EventType.CLICK, () => { // This click is outside the menubar so it counts as a focus out if (this.isFocused) { this.setUnfocusedState(); } })); </ins> } this.container.on(EventType.FOCUS_IN, (e) => {

Discussion:
Issue Type: <bBug</bWhen using the custom title bar and the toggled menu bar setting, the menu bar becomes stuck in the toggled on state. This primarily occurs when the active VS Code window becomes inactive while the menu bar is toggled on. When using multiple VS Code windows this makes it difficult to identify the correct window because the title bar's filename information is hidden. Steps to reproduce: the setting to , and setting to VS Code is the active window, hold down the key to show the menu bar the key while still holding the key to switch to another application. The active VS Code window becomes inactive and the menu bar is visible. Alternatively you can click outside of the active VS Code window while the menu bar is being displayed. VS Code version: Code 1.25.0 (, 2018-07-05T13:11:58.697Z) OS version: Windows_NT x64 10.0. <details<summaryExtensions (4)</summaryExtensionVersion ------ classic-asp0.0.4 vscode-icon-theme1.6.2 csharp1.15.2 PowerShell1.8.0 </details<!-- generated by issue reporter --
(Experimental duplicate detection) Thanks for submitting this issue. Please also check if it is already covered by an existing one, like: <!-- score: 0.538 --- <!-- score: 0.491 --- <!-- score: 0.483 --- <!-- score: 0.482 --- <!-- score: 0.48 --<!-- potentialduplicatescomment --
Change:
return text.replace(/[`*_{}[]()#+-.!]/g, '$&'); // escape markdown syntax tokens: http://daringfireball.net/projects/markdown/syntax#backslash } <ins> export function removeMarkdownEscapes(text: string): string { if (!text) { return text; } return text.replace(/([`*_{}[]()#+-.!])/g, '$1'); } </ins> export interface IHTMLContentElement { /**

Discussion:
According to and . should be used to escape a dot. However, it looks like our hover renderer doesn't unescape the dot when in a link !
Sorry to bother yall but is there an ETA on this? I'm hoping to release/publicize a project soon that relies heavily on json-schemas but I don't want to publicize it until this is fixed (because it will be a bad UX and I want people to have good experience the first time they try the thing). Thanks
From a quick look, the root cause may be the processing we do in the js extension for files: Can you please share an example json file that shows this in the latest builds. Thanks.
Verifying bug on master, latest commit ! See my original ticket for repro steps
Verified in code.
I still see unescaped characters: ! I created
Verified fix on master @ Thanks! Side question: how do changes like this get into release, i.e. when might one expect this change to be deployed to users?
Change:
display: initial !important; } <del> .interactive-result-code-block { </del> <ins> .interactive-item-container .value .rendered-markdown [data-code] { </ins> margin: 16px 0; }

Discussion:
Due to rearranging things, this rule adds a margin to a child element not matched by That first rule should target the parent element, but we can't do that because we don't know that the parent element is a codeblock. the codeblock container came out of the markdown rendered with a class but it was removed by this sanitization: Can I change that to keep the code class? Why do we sanitize class names?
Removing classnames prevents rendered markdown from unexpectedly picking up styling from core VS Code. There are two main concerns : It leaks our implementation to extensions/user content which makes changes more difficult It could enable an attack where untrusted content is able to render a link or similar just like our UI which users will intuitively trust For sanitization, can you pass in an allowlist that just includes the classnames you want to preserve?
Makes sense, I can use an allowlist
Friendly ping! Looks like this issue requires some further steps to be verified. Please provide us with the steps necessary to verify this issue.
Change:
return true; } <ins> // Get the abbreviation right now // Fixes https://github.com/microsoft/vscode/issues/74505 // Stylesheet abbreviations starting with @ should bring up suggestions // even at outer-most level const abbreviation = document.getText(new vscode.Range(abbreviationRange.start.line, abbreviationRange.start.character, abbreviationRange.end.line, abbreviationRange.end.character)); if (abbreviation.startsWith('@')) { return true; } </ins> // Fix for https://github.com/microsoft/vscode/issues/34162 // Other than sass, stylus, we can make use of the terminator tokens to validate position if (syntax !== 'sass' && syntax !== 'stylus' && currentNode.type === 'property') { // Fix for upstream issue https://github.com/emmetio/css-parser/issues/3 if (currentNode.parent && currentNode.parent.type !== 'rule'

Discussion:
Note: char disable tab after it with setting even with custom snippet the not trigger because char disable tab after it.
closedWith
Actually, reopening since I realized the extension isn't allowing the abbreviations outside of surrounding braces. the latest Emmet doesn't allow + in the expansions now, so you'd have to create custom snippets (with names that don't have +) to get that old behaviour back.
"+" Cheats| 1- 2- 3- 4- 5- 6- 7- 8- 9- 10- 11- 12- 13- 14- 15- 16- 17- 18- 19- 20- 21- 22- 23-
I'm aware there were a lot of snippets with +. The Emmet documentation website is currently outdated. See and
Sorry I didn't know that.
Verifier: verify that in an empty stylesheet document (e.g. CSS), , , , and all have an Emmet suggestion showing up.
Change:
protected _taskRunningState: IContextKey<boolean>; <ins> private _inProgressTasks: Set<string> = new Set(); </ins> protected _outputChannel: IOutputChannel; protected readonly _onDidStateChange: Emitter<ITaskEvent>; private _waitForSupportedExecutions: Promise<void>;

Discussion:
<img width="423" alt="image" src="https://user-"
I am unable to repro this - could you pls provide the steps that you take?
I have not found a pattern so far, might be timing related. It is not happening everytime I reload the window... However, one thing to keep in mind is that I often use and not . That command kills the build task and relaunches it: So that may well be related to the issue.
Thanks for the idea, but seems unrelated to that command as has reproduced this with
Change:
adjustWhitespace: !(suggestion.insertTextRules! & CompletionItemInsertTextRule.KeepWhitespace) }); <ins> scrollState.restoreRelativeVerticalPositionOfCursor(this.editor); </ins> if (!(flags & InsertFlags.NoAfterUndoStop)) { this.editor.pushUndoStop(); }

Discussion:
<!-- Do Not Delete This! featurerequesttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --<!-- Describe the feature you'd like. --I would like an option to virtually prevent vscode from pushing down the current focused line when new lines are automatically . For example, when I click to automatically add an import, vscode adds the import line and the current focused line is scrolled down. This causes a distraction because the line I'm working on is moved away even tho I didn't want to scroll. Here is a gif showing how IntelliJ behavior when new lines are automatically above the current selected line. Note that after the import statement is the current line is virtually kept the same (the line number do change, of course, but the scroll is set to a new position in order to respect the old position): ! The next gif show how vscode pushes down the code and loses the previous virtual position: ! Would be possible to add an option to vscode behavior like IntelliJ in this situation?
Technically, the editor does not scroll. The scrollTop is maintained. It just happens that everything is pushed down by the auto-import which inserts a line at the top of the file. This can be done from the outside if you know there are edits unrelated to the current cursor position in the suggestion e.g.:
I'd like to help out with this! Any additional pointers would be appreciated.
This is where the first potential edit happens: and this is where it is done: So, those two places should be used to capture and restore the scroll state
to verify: down a bit a typescript suggestion that adds an import sure that the scroll position stays stable (lines aren't pushed down)
Change:
import { Disposable, dispose, IDisposable, MutableDisposable } from 'vs/base/common/lifecycle'; import { IInstantiationService } from 'vs/platform/instantiation/common/instantiation'; import { normalizeDriveLetter } from 'vs/base/common/labels'; <del> import { IRange } from 'vs/editor/common/core/range'; </del> export interface IResourceLabelProps { resource?: URI | { primary?: URI; secondary?: URI }; name?: string | string[]; <del> range?: IRange; </del> description?: string; }

Discussion:
Type: <bBug</bis used as delimiter instead of <img width="499" alt="image" src=""VS Code version: Code - Insiders 1.84.0-insider (, 2023-10-23T05:35:37.619Z) OS version: Darwin arm64 23.0.0 Modes: <details<summarySystem Info</summary </details<details<summaryExtensions (20)</summaryExtensionVersion ------ project-manager12.7.0 vscode-eslint2.4.2 gitlens14.4.0 EditorConfig0.16.4 vscode-todo-plus4.19.1 code-runner0.12.1 vscode-pull-request-github0.74.0 gitlab-workflow3.81.0 vscode-peacock4.2.2 vscode-random1.11.0 rainbow-csv3.8.0 dotenv1.0.1 remote-containers0.318.0 remote-ssh0.107. remote-explorer0.5. material-icon-theme4.31.0 partial-diff1.4.3 code-spell-checker3.0.1 sort-lines1.11.0 markdown-all-in-one3.5.1 (1 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
Please use the command to investigate possible cause.
I am seeing it in Explorer too, in today's Insider, with all extensions disabled: !
I am bisecting now...
Hmm, nothing found. Maybe I am doing it wrong.
From
Change:
import { IEditorContribution } from 'vs/editor/common/editorCommon'; import { ITextModel } from 'vs/editor/common/model'; import { IDialogService } from 'vs/platform/dialogs/common/dialogs'; <ins> import { basename } from 'vs/base/common/resources'; </ins> const ignoreUnusualLineTerminators = 'ignoreUnusualLineTerminators';

Discussion:
Version: 1.58.0-insider Commit: Date: 2021-06-16T05:18:57.982Z Electron: 12.0.11 Chrome: 89.0.4389.128 14.16.0 V8: 8.9.255.25-electron.0 OS: Linux x64 5.11.0-18-generic After starting up VS Code I got a modal dialog telling me about an unusual line delimiter. It didn't tell me about the file this is about. ! After accepting to fix, I saw where the problem was ! I find the dialog too heavy, especially on startup. I would need to see the code to find out what's the issue here. E.g. in our case, this is in a test, so might be intended Maybe have a warning triage next to 'LF' in the status bar? When I click ignore for this file, how can I unignore the file?
I agree this is pretty weird. The prompt comes from a code editor contribution which executes only when a code editor widget is instantiated and shows the problematic file. I think that this normally works fine, but in this case I believe the problematic file was opened, the dialog was shown, and then the "Release Notes" editor opened under the prompt and changed the active editor from under the prompt. I agree with the feedback here, but I'm not sure what to do. Maybe we could make the "Release Notes" editor wait until all confirm dialogs have been closed before showing itself or that the workbench starts directly with that editor after a release? Regarding converting this to a passive indicator in the status bar: I don't think that would be wise. Having this unusual line terminator will lead to semantic tokens, jump to definition and all kind of language features to become off. Here is the background:
Maybe instead of a modal dialog this could be shown somewhere in the editor area? Almost like the trust banner but instead of showing to the top of the window, showing right above the editor but still inside the editor? ! As for release notes, I think we are investigating to move away from using an editor and using something else but I cannot find the issue now. Arguably this can happen in other cases too I guess, e.g.

when I open a file which loads slow and I manage to open another editor over it?
Well, easiest fix is to add the file name into the dialog, I would argue then it doesn't really matter which editor is active.
PR is up to change the dialog just a bit (): !
Change:
@command('git.commitStagedAmend', { repository: true }) async commitStagedAmend(repository: Repository): Promise<void> { <del> await this.commitWithAnyInput(repository, { all: false, amend: true }); </del> <ins> let msg; if (repository.HEAD) { if (repository.HEAD.commit) { let id = repository.HEAD.commit; let commit = await repository.getCommit(id); msg = commit.message; } } await this.commitWithAnyInput(repository, { all: false, amend: true, defaultMsg: msg }); </ins> } @command('git.commitAll', { repository: true })

Discussion:
VSCode Version: Code - Insiders 1.17.0-insider (, 2017-09-26T05:24:48.911Z) OS Version: Windows_NT x64 10.0. Extensions: none Testing Steps to Reproduce: some change Staged (Amend) I'm asked for a new commit message without the existing one as the default. I usually want to keep the existing one.
yeah may be we can add an option to keep the older message. I mean prefill the text box with the latest commit message..
I'm assuming this is not in version 1.18.1. Can I expect this in 1.18.2? Because I'm looking for this to amend the commit properly (both the diff and the message). I keep having to go back to the command line and issue because VSCode's Commit Staged (Amend) option shows a blank message.
No, this will be in 1.19.
I upgrade to 1.19, and this works, however we use gerrit which has a Change-Id in the commit message, and the newline is removed when to the commit message box. Which means when I upload the change to gerrit, it becomes a new patchset. Can this please not remove the newlines.
I see... I created this to track that issue:
Change:
assertUSLabel(OperatingSystem.Linux, KeyMod.CtrlCmd | KeyCode.KEY_A, 'Ctrl+A'); assertUSLabel(OperatingSystem.Linux, KeyMod.Shift | KeyCode.KEY_A, 'Shift+A'); assertUSLabel(OperatingSystem.Linux, KeyMod.Alt | KeyCode.KEY_A, 'Alt+A'); <del> assertUSLabel(OperatingSystem.Linux, KeyMod.WinCtrl | KeyCode.KEY_A, 'Windows+A'); </del> <ins> assertUSLabel(OperatingSystem.Linux, KeyMod.WinCtrl | KeyCode.KEY_A, 'Super+A'); </ins> // two modifiers assertUSLabel(OperatingSystem.Linux, KeyMod.CtrlCmd | KeyMod.Shift | KeyCode.KEY_A, 'Ctrl+Shift+A'); assertUSLabel(OperatingSystem.Linux, KeyMod.CtrlCmd | KeyMod.Alt | KeyCode.KEY_A, 'Ctrl+Alt+A'); <del> assertUSLabel(OperatingSystem.Linux, KeyMod.CtrlCmd | KeyMod.WinCtrl | KeyCode.KEY_A, 'Ctrl+Windows+A'); </del> <ins> assertUSLabel(OperatingSystem.Linux, KeyMod.CtrlCmd | KeyMod.WinCtrl | KeyCode.KEY_A, 'Ctrl+Super+A'); </ins> assertUSLabel(OperatingSystem.Linux, KeyMod.Shift | KeyMod.Alt | KeyCode.KEY_A, 'Shift+Alt+A'); <del> assertUSLabel(OperatingSystem.Linux, KeyMod.Shift | KeyMod.WinCtrl | KeyCode.KEY_A, 'Shift+Windows+A'); assertUSLabel(OperatingSystem.Linux, KeyMod.Alt | KeyMod.WinCtrl | KeyCode.KEY_A, 'Alt+Windows+A'); </del> <ins> assertUSLabel(OperatingSystem.Linux, KeyMod.Shift | KeyMod.WinCtrl | KeyCode.KEY_A, 'Shift+Super+A'); assertUSLabel(OperatingSystem.Linux, KeyMod.Alt | KeyMod.WinCtrl | KeyCode.KEY_A, 'Alt+Super+A'); </ins> // three modifiers assertUSLabel(OperatingSystem.Linux, KeyMod.CtrlCmd | KeyMod.Shift | KeyMod.Alt | KeyCode.KEY_A, 'Ctrl+Shift+Alt+A'); <del> assertUSLabel(OperatingSystem.Linux, KeyMod.CtrlCmd | KeyMod.Shift | KeyMod.WinCtrl | KeyCode.KEY_A, 'Ctrl+Shift+Windows+A'); assertUSLabel(OperatingSystem.Linux, KeyMod.CtrlCmd | KeyMod.Alt | KeyMod.WinCtrl | KeyCode.KEY_A, 'Ctrl+Alt+Windows+A'); assertUSLabel(OperatingSystem.Linux, KeyMod.Shift | KeyMod.Alt | KeyMod.WinCtrl | KeyCode.KEY_A, 'Shift+Alt+Windows+A'); </del> <ins> assertUSLabel(OperatingSystem.Linux, KeyMod.CtrlCmd | KeyMod.Shift | KeyMod.WinCtrl | KeyCode.KEY_A, 'Ctrl+Shift+Super+A'); assertUSLabel(OperatingSystem.Linux, KeyMod.CtrlCmd | KeyMod.Alt | KeyMod.WinCtrl | KeyCode.KEY_A, 'Ctrl+Alt+Super+A'); assertUSLabel(OperatingSystem.Linux, KeyMod.Shift | KeyMod.Alt | KeyMod.WinCtrl | KeyCode.KEY_A, 'Shift+Alt+Super+A'); </ins> // four modifiers <del> assertUSLabel(OperatingSystem.Linux, KeyMod.CtrlCmd | KeyMod.Shift | KeyMod.Alt | KeyMod.WinCtrl | KeyCode.KEY_A, 'Ctrl+Shift+Alt+Windows+A'); </del> <ins> assertUSLabel(OperatingSystem.Linux, KeyMod.CtrlCmd | KeyMod.Shift | KeyMod.Alt | KeyMod.WinCtrl | KeyCode.KEY_A, 'Ctrl+Shift+Alt+Super+A'); </ins> // chord assertUSLabel(OperatingSystem.Linux, KeyChord(KeyMod.CtrlCmd | KeyCode.KEY_A, KeyMod.CtrlCmd | KeyCode.KEY_B), 'Ctrl+A Ctrl+B');

Discussion:
I am actually surprised this bug exists, aren't you using some keybinding helper to turn the keybinding into a human readable label?
yea I'm using the keybinding service, yes, I'm not doing anything special on my own I don't believe.
Related:
PR out:
Change:
keyboardNavigationLabelProvider: instantiationService.createInstance(TreeKeyboardNavigationLabelProvider), accessibilityProvider: instantiationService.createInstance(ListAccessibilityProvider), filter: this.filter, <ins> findWidgetEnabled: false </ins> }) as WorkbenchObjectTree<TestExplorerTreeElement, FuzzyScore>; this._register(this.tree.onDidChangeCollapseState(evt => {

Discussion:
Type: <bBug</bFilter tests for the current doc is no longer working. is doing nothing in the test explorer. It seems that all filter are broken. For example is also not possible. <img width="344" alt="CleanShot 2022-07-25 at 11 14 38 src="https://user-"VS Code version: Code - Insiders 1.70.0-insider (Universal) (, 2022-07-25T05:27:27.755Z) OS version: Darwin x64 21.5.0 Modes: <details<summarySystem Info</summary </detailsExtensions disabled<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
/assign
Change:
}; that.telemetryService.publicLog2<ContinueEditSessionEvent, ContinueEditSessionClassification>('editSessions.continue.store'); <del> // Run the store action to get back a ref const ref = await that.storeEditSession(false); </del> let uri = workspaceUri ?? await that.pickContinueEditSessionDestination(); if (uri === undefined) { return; } <ins> // Run the store action to get back a ref const ref = await that.storeEditSession(false); </ins> // Append the ref to the URI if (ref !== undefined) { const encodedRef = encodeURIComponent(ref);

Discussion:
edit sessions enabled in settings Continue Working On command in 't pick a destination, esc to dismiss the quickpick Show Edit Sessions command :bug: edit session was created anyway
I'm seeing no options !
Prior to that, I saw this prompt and clicked cancel, then saw an error notification related to that about not being able to save files. !
worked in
Change:
'xterm-addon-canvas': `${baseNodeModulesPath}/xterm-addon-canvas/lib/xterm-addon-canvas.js`, 'xterm-addon-image': `${baseNodeModulesPath}/xterm-addon-image/lib/xterm-addon-image.js`, 'xterm-addon-search': `${baseNodeModulesPath}/xterm-addon-search/lib/xterm-addon-search.js`, <ins> 'xterm-addon-serialize': `${baseNodeModulesPath}/xterm-addon-serialize/lib/xterm-addon-serialize.js`, </ins> 'xterm-addon-unicode11': `${baseNodeModulesPath}/xterm-addon-unicode11/lib/xterm-addon-unicode11.js`, 'xterm-addon-webgl': `${baseNodeModulesPath}/xterm-addon-webgl/lib/xterm-addon-webgl.js`, '@vscode/iconv-lite-umd': `${baseNodeModulesPath}/@vscode/iconv-lite-umd/lib/iconv-lite-umd.js`,

Discussion:
Type: <bBug</bOpen terminal Use Terminal Copy Selecton as HTML command () after selecting text in terminal Expected: Selected text in the terminal is copied as html, so formatting (such as color) is kept. I am then able to paste this text elsewhere, outside of VS Code. Actual: [object event] notifcation] & text isn't copied to clipboard at all, clipboard contents remain unchanged VS Code version: Code 1.78.2 (, 2023-05-10T14:39:26.248Z) OS version: WindowsNT x64 10.0. Modes: Sandboxed: Yes <details<summarySystem Info</summary </details<details<summaryExtensions (16)</summaryExtensionVersion ------ npm-intellisense1.4.4 vscode-eslint2.4.0 vscode-npm-script0.3.29 prettier-vscode9.12.0 npm1.3.0 vscode-ansi1.1.6 python2023.8.0 vscode-pylance2023.5.30 jupyter2023.4. jupyter-keymap1.1.0 jupyter-renderers1.0.15 vscode-jupyter-cell-tags0.1.8 vscode-jupyter-slideshow0.1.5 vscode-react-native1.11.0 vscode-react-native-preview2023.5.821 es7-react-js-snippets1.9.3 </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
This was working at some pt, not sure why it doesn't anymore
Can reproduce: ! It's also a little weird having in the precondition as that makes it never show up in the command palette (I'm guessing that's set to false when the terminal is blurred?)
Something's wrong with getting the serialize addon: !