spikerj/spikersoft-issues
1
0
Fork 0
Code Issues 196 Pull Requests Actions Packages Projects Releases Wiki Activity

[Enhancement] C# playground: Roslyn / dotnet formatter for Monaco #38

New Issue
Open
opened 2026-04-28 23:48:47 +00:00 by spikerj · 0 comments
spikerj commented 2026-04-28 23:48:47 +00:00
Owner
Copy Link
Copy Source

Summary

Provide C# formatting aligned with dotnet format / Roslyn conventions for the Monaco C# playground model.

Approach candidates

A. Roslyn formatter on existing backend compilation path — reuse same service that emits diagnostics (single round-trip).
B. WASM-only path if Mono/.NET toolchain exposes Microsoft.CodeAnalysis.Formatting compatible API in WASM debug story — only if bundled cost acceptable.
C. Degrade gracefully: formatter unavailable offline → tooltip explains.

Integration

  • Register provider for csharp (or our Monaco language id for .cs).
  • Preserve PDB line mapping / project layout context if formatting affects multi-file advanced sandbox (only format active file vs whole solution — specify behavior).

Dependency

Platform Format toolbar + Monaco #24 + #33 WASM/Roslyn context may intersect — coordinate breakpoints vs format ordering.

## Summary Provide **C#** formatting aligned with **`dotnet format`** / **Roslyn** conventions for the Monaco C# playground model. ## Approach candidates **A.** **Roslyn** formatter on **existing backend** compilation path — reuse same service that emits diagnostics (single round-trip). **B.** WASM-only path if Mono/.NET toolchain exposes **`Microsoft.CodeAnalysis.Formatting`** compatible API in WASM debug story — only if bundled cost acceptable. **C.** Degrade gracefully: formatter unavailable offline → tooltip explains. ## Integration - Register provider for **`csharp`** (or our Monaco language id for `.cs`). - Preserve **PDB line mapping** / project layout context if formatting affects multi-file advanced sandbox (only format active file vs whole solution — specify behavior). ## Dependency Platform Format toolbar + Monaco `#24` + `#33` WASM/Roslyn context may intersect — coordinate breakpoints vs format ordering.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
agentic
Actionable surfaced by the agentic architecture & security review
 bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 sonarqube
Code quality issue surfaced by SonarQube (bug / code smell)
 wontfix
This won't be fixed
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
spikerj (Joseph Spiker)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: spikerj/spikersoft-issues#38