feat(reader): remove ParseNode infrastructure#2852
Conversation
6526d29 to
a2858a9
Compare
Refactor OpenAPI parsing to use System.Text.Json JsonNode APIs directly with explicit ParsingContext propagation, replacing the ParseNode wrapper hierarchy. Co-authored-by: Copilot <[email protected]>
Co-authored-by: Copilot <[email protected]>
Co-authored-by: Copilot <[email protected]>
Co-authored-by: Copilot <[email protected]>
e2ad32e to
0fec6aa
Compare
Code Coverage OverviewLanguages: C# C# / code-coverage/dotnetThe overall coverage in the branch remains at 42%, unchanged from the branch. Show a code coverage summary of the most impacted files.
Updated |
gavinbarron
left a comment
There was a problem hiding this comment.
most of the comments about dicards/casing and unused parameters apply broadly.
Although you have explained the unused parameters in a side chat, so disregard those comments
Co-authored-by: Copilot <[email protected]>
Co-authored-by: Copilot <[email protected]>
Co-authored-by: Copilot <[email protected]>
Signed-off-by: Vincent Biret <[email protected]>
|




Summary
Benchmark Comparison vs Vincent Biret's Last Update (eb1258a)
Hardware difference:
Results comparison (Vincent → Current):
Gen0/Gen1 GC collections: Similar or slightly lower across all benchmarks.
Key takeaway: The refactored code shows significant improvements in both execution time (30-45% faster) and memory allocation (15-50% less). However, note this is not an apples-to-apples comparison due to different hardware (ARM vs x64) and runtime versions. For a true performance assessment, you'd need to rerun Vincent's baseline commit on the same Snapdragon X hardware.
Validation