Skip to content

feat: XML value type correction via xsi:type / XSD (2.0.0, breaking) #37

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jefim wants to merge 6 commits into
base: main
Choose a base branch
from
Open

feat: XML value type correction via xsi:type / XSD (2.0.0, breaking) #37

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
c26521b
feat: add XML value type correction (xsi:type / XSD) [2.0.0]
jefim May 27, 2026
976139b
feat: add ActionOnBadValues option for strict type correction
jefim May 28, 2026
3c7dca7
fix: address PR #37 review feedback
jefim May 28, 2026
a87ef9f
feat: add xsi:nil support for empty-element handling
jefim May 29, 2026
4349618
feat: add string type handling for XML element in unit tests
jefim May 29, 2026
73dd783
fix: correct formatting in unit test assertions for XML string values
jefim May 29, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions Frends.JSON.ConvertXMLStringToJToken/CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,15 @@
# Changelog

## [2.0.0] - 2026-05-27
### Breaking
- The `XSD` parameter has moved from the **Input** tab to the **Options** tab and is now only used (and shown) when `TypeCorrection` is `Schema`.
- **Why this is breaking:** the XSD is no longer bound where existing process references expect it. A migration (`migration.json`) ships with the package to copy `Input.XSD` → `Options.XSD` and set `TypeCorrection = Schema` automatically, but **tenants that do not apply migration.json will not migrate automatically**. On those tenants the old XSD value is dropped, so XSD-driven array mapping (added in 1.2.0) silently stops working.
- **Upgrade path (manual, for tenants without migration support):** after updating each affected process step, open the **Options** tab, set `TypeCorrection = Schema`, and paste your XSD into `Options.XSD`. This restores the previous array-mapping behaviour. Steps that never used an XSD need no changes — leave `TypeCorrection = None`.
### Added
- Added `Options` parameter with `TypeCorrection` (`None`/`Attributes`/`Schema`) to convert numeric and boolean XML values into native JSON types, via inline `xsi:type` attributes (`Attributes`) or the supplied XSD (`Schema`). Default is `None`.
### Changed
- In `Schema` mode the XSD now drives both array mapping and value typing. `Schema` mode without an XSD is a graceful no-op (returns string values) rather than an error.

## [1.2.0] - 2026-05-07
### Added
- Added optional XSD input support to ensure consistent array/object mapping
Expand Down
Loading
Loading