Boshen
Boshen
I double checked all the existing parsers, all of them decode expect tsc. I'll split it - decode in lexer, whitespace in transformer.
@overlookmotel I can no longer figure out the proper way of doing this. I'll leave this to you. You need to move https://github.com/oxc-project/oxc/blob/c6312915dfb377a0f6aad8d9b4beb04d7eccd780/crates/oxc_transformer/src/jsx/jsx_impl.rs#L996-L1046 to https://github.com/oxc-project/oxc/blob/c6312915dfb377a0f6aad8d9b4beb04d7eccd780/crates/oxc_parser/src/lexer/jsx.rs#L79-L99 with a new method `read_jsx_text`.
> One question: In codegen, what characters do we need/want to encode as `&...;`? > > I guess shortest legal output is only to encode ``, `{`, and `}`. Need...
All setup is ready here https://github.com/oxc-project/monitor-oxc
Runtime test is in https://github.com/oxc-project/monitor-oxc/blob/main/src/main.test.mjs
Close as stale given no progress has been made, but feel free to implement fixers when needed.
Is this just `String`? @overlookmotel said it could just be a string but I didn't spend the time converting it.
### Merge activity * **Oct 13, 5:14 AM EDT**: The merge label '0-merge' was detected. This PR will be added to the [Graphite merge queue](https://app.graphite.dev/merges?org=oxc-project&repo=oxc) once it meets the requirements....
The usual drill for this is @Dunqing will dig into tsc to find the matching resolution code. He's on holiday so we'll have to wait a bit.
See https://github.com/oxc-project/oxc/tree/main/apps/oxlint/src/output_formatter