Skip to content

fix: make protected members public to resolve mangler build errors#310195

Open
NikolaRHristov wants to merge 2 commits intomicrosoft:mainfrom
CodeEditorLand:fix-310191
Open

fix: make protected members public to resolve mangler build errors#310195
NikolaRHristov wants to merge 2 commits intomicrosoft:mainfrom
CodeEditorLand:fix-310191

Conversation

@NikolaRHristov
Copy link
Copy Markdown

setEditorVisible in editorPane.ts and _enableCommandLineSandboxRewriting in runInTerminalTool.ts were declared as protected but accessed publicly by subclasses (chatDebugEditor.ts and runInTerminalConfirmationTool.ts respectively), causing the mangler to promote them to public and then error with "Protected fields have been made PUBLIC".

Explicitly mark both members as public to satisfy the mangler and allow compile-build-with-mangling to complete successfully.

Fixes #310191

`setEditorVisible` in `editorPane.ts` and `_enableCommandLineSandboxRewriting`
in `runInTerminalTool.ts` were declared as `protected` but accessed publicly
by subclasses (`chatDebugEditor.ts` and `runInTerminalConfirmationTool.ts`
respectively), causing the mangler to promote them to public and then
error with "Protected fields have been made PUBLIC".

Explicitly mark both members as `public` to satisfy the mangler and
allow `compile-build-with-mangling` to complete successfully.

Fixes microsoft#310191
@NikolaRHristov
Copy link
Copy Markdown
Author

@microsoft-github-policy-service agree company="PlayForm"

@vs-code-engineering
Copy link
Copy Markdown
Contributor

vs-code-engineering bot commented Apr 15, 2026

📬 CODENOTIFY

The following users are being notified based on files changed in this PR:

@bpasero

Matched files:

  • src/vs/workbench/browser/parts/editor/editorPane.ts

@pwang347
Copy link
Copy Markdown
Member

@NikolaRHristov thanks for opening a PR, I think we should just add override to the subclasses though right?

@NikolaRHristov
Copy link
Copy Markdown
Author

@bpasero bpasero assigned bpasero and unassigned pwang347 Apr 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ERROR: Protected fields have been made PUBLIC.

3 participants