microsoft / microsoft/monaco-editor

[Feature Request] expose API for modifying configurations in standalone mode

Open
#4,095 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature-request tokenization
Dominant language
JavaScript
Stars
46.8k
Forks
4.1k
Avg merge
17h 58m
Merged PRs (30d)
1

Description

Context
  • This issue is not a bug report. (please use a different template for reporting a bug)
  • This issue is not a duplicate of an existing issue. (please use the search to find existing issues)
Description

here's the background of this request: https://stackoverflow.com/questions/76738291/update-monaco-editor-configurations-in-standalone-browser-editor

in short, I'm finding a way to do this properly:

import { IConfigurationService } from "monaco-editor/esm/vs/platform/configuration/common/configuration";
import { StandaloneServices } from "monaco-editor/esm/vs/editor/standalone/browser/standaloneServices";

(()=>{
  StandaloneServices.get(IConfigurationService).updateValue(
    "editor.maxTokenizationLineLength", 40000
  );
})();
Monaco Editor Playground Link

No response

Monaco Editor Playground Code

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the standalone configuration entry points referenced in the issue: IConfigurationService and StandaloneServices. Trace how standalone browser editors currently expose configuration changes and determine the public API surface needed for updating editor.maxTokenizationLineLength. Done means the supported standalone API is documented and can modify configurations without relying on internal imports.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
api, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.