Can you provide before/after example snippets?

@stefanmedack or just the API URL where this happens

curl -v -H "CONTENT-TYPE: application/json" 'https://media.ccc.de/public/events/search?q=ccc&page=2' | jq '.events[] | .metadata'

gives a list of these:

{
  "related": {
    "2983": 2,
    "3466": 2,
    "3493": 2
  },
  "remote_id": "7726"
}

That change was required i.e. to prune weak related entries periodically: https://github.com/voc/voctoweb/blob/master/lib/update_related_events.rb#L16

I'm sorry if that broke your application, but it is a required change. Can't you just call {}.keys() or something?

Okay, in this case that is unfortunate for us. But again: wouldn't it make sense to still use a list of objects. So I would suggest to change the structure to

{
  "related": [
     {
         "eventId" : "2983": 
         "whateverThisValueIsFor": 2
     },
     {
         "eventId" : "3466": 
         "whateverThisValueIsFor": 2
     }
  ],
  "remote_id": "7726"
}

I don't think it would make sense to change that for voctoweb internally?
By using a hash data structure (id: weight) voctoweb gets unique keys and merging based on keys for free.

I would consider a PR which change this externally for API clients in the view at app/views/public/shared/_event.json.jbuilder.

@manno Do I correctly understand that you would be fine with changing the public API for public/events/ to output the following:

...
{
  "related": [
     {
         "event_id" : "2983",
         "weight": 2
     },
     {
         "event_id" : "3466",
         "weight": 2
     }
  ],
  "remote_id": "7726"
}

It would be great to get help with how to modify the builder with regards to the related property. It is not mentioned in the json builder. Are you using the master branch for production?

Idea for the future: We should thinking about solving such issues with a new GraphQL based API endpoint.

✅ Fixed in the c3media-base client library here. /cc @stefanmedack