René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Feature.Id only supports String type","articleBody":"Hello!\n\nAccording to https://datatracker.ietf.org/doc/html/rfc7946#section-3.2, the `Id` field of the `Feature`, if present, can be either number or string:\n\u003e If a Feature has a commonly used identifier, that identifier\n\u003e SHOULD be included as a member of the Feature object with the name\n\u003e \"id\", and the value of this member is either a JSON string or\n\u003e number.\n\nHowever, current implementation only supports deserialization of string values for this field.\nProposed solutions:\n* A custom JSON converter for this field, with storing the value as a `string`.\n* Storing the value as a discriminated union of `string` and `int` (or `long`).\n\nBest regards,\nDmitry","author":{"url":"https://github.com/dmitry-kandiner","@type":"Person","name":"dmitry-kandiner"},"datePublished":"2025-08-06T12:57:40.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/35/GeoJSON.Text/issues/35"}