[playground]: Fix non‑BMP code point handling in quick‑fixes and markers

[danparizher]

Summary

Fixes #16266

Updated the playground to convert UTF‑32 (code point) columns from the WASM diagnostics/fixes into Monaco’s UTF‑16 columns when constructing both quick‑fix edit ranges and diagnostic markers in playground/ruff/src/Editor/SourceEditor.tsx.

With this change, applying the C408 quick fix on dict(𠤪=1) now correctly yields {"𠤪": 1} without leaving a stray ).

[MichaReiser]

Thank you. I think I'd prefer to handle this the same way as we do in ty: That is, implement the conversion in ruff_wasm. The benefit of this is that downstream ruff_wasm users also benefit from this change (I suspect that most downstream users use JS too and would require the exact same conversion).

See

ruff/crates/ty_wasm/src/lib.rs

Lines 88 to 92 in a9b6618

	pub fn new(
	root: &str,
	position_encoding: PositionEncoding,
	options: JsValue,
	) -> Result<Workspace, Error> {

[github-actions]

ruff-ecosystem results

Linter (stable)

✅ ecosystem check detected no linter changes.

Linter (preview)

✅ ecosystem check detected no linter changes.

[MichaReiser]

This works but it will break existing clients that assumed UTF8.

I suggest adding positionEncoding a new argument to new (similar to ty) and storing it on the Workspace and then using it here.

This allows each user to use the encoding that best suits their use case.

[MichaReiser]

Thanks. this is great