Skip to content

Handle OSM JSON version as string#159

Open
charliesheh wants to merge 1 commit into
OsmSharp:developfrom
charliesheh:fix-158-osm-json-version-string
Open

Handle OSM JSON version as string#159
charliesheh wants to merge 1 commit into
OsmSharp:developfrom
charliesheh:fix-158-osm-json-version-string

Conversation

@charliesheh
Copy link
Copy Markdown

Fixes deserialization of OSM JSON when the version field is provided as a string instead of a numeric value.

Example:

{
  "version": "0.6"
}

Changes Made:

  • Updated OsmJsonConverter to support both numeric and string values for version
  • Added regression test for string-based version parsing

Fixes #158

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

System.Text.Json.JsonException when parsing response of type Osm

1 participant