[openstreetmap/openstreetmap-website] Implement JSON support for the changeset download API (PR #5973)

[Kyℓe Hensel]

k-yle left a comment (openstreetmap/openstreetmap-website#5973)

for completeness, another option that hasn't been mentioned yet is:

```jsonc
{
  "osmChange": [
    { "type": "create", "elements": [a, b, c] },
    { "type": "delete", "elements": [d, e] },
    { "type": "modify", "elements": [f, g] },
    { "type": "delete", "elements": [h, i], "ifUnused": true },
  ],
  // extra properties for 'options' or 'changesetTags' or whatever could go here
}
```

this would address all the limitations from the other proposals, _and_ avoids adding properties to the `Node`/`Way`/`Relation` objects[^1]

[^1]: in my opinion, we should avoid adding temporary properties to these objects, because this could become messy and could be weird to implement in a type-safe way in some languages

-- 
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/5973#issuecomment-2849262386
You are receiving this because you are subscribed to this thread.

Message ID: <openstreetmap/openstreetmap-website/pull/5973/c2849262386 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20250504/8272f281/attachment.htm>