[core-http] Make XML parse/deserialization a separate optional package #8616

xirzec · 2020-04-30T00:09:56Z

Most services don't use XML, so it's a really heavy dependency to drag in. Clients who require XML should optionally compose a pipeline that deserializes it correctly using a core-xml package or similar.

Related to #8617

xirzec added Client This issue points to a problem in the data-plane of the library. Azure.Core labels Apr 30, 2020

xirzec added this to the [2020] June milestone Apr 30, 2020

xirzec self-assigned this Apr 30, 2020

xirzec mentioned this issue Apr 30, 2020

[Epic][core-http] Planned improvements / redesigns #8535

Closed

35 tasks

xirzec modified the milestones: [2020] June, [2020] July Jun 8, 2020

xirzec modified the milestones: [2020] July, [2020] October, [2020] August Jul 7, 2020

xirzec mentioned this issue Jul 28, 2020

[core-xml] Create @azure/core-xml #10307

Merged

xirzec closed this as completed in #10307 Jul 30, 2020

github-actions bot locked and limited conversation to collaborators Apr 12, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[core-http] Make XML parse/deserialization a separate optional package #8616

[core-http] Make XML parse/deserialization a separate optional package #8616

xirzec commented Apr 30, 2020 •

edited

Loading

[core-http] Make XML parse/deserialization a separate optional package #8616

[core-http] Make XML parse/deserialization a separate optional package #8616

Comments

xirzec commented Apr 30, 2020 • edited Loading

xirzec commented Apr 30, 2020 •

edited

Loading