{"push_id":3112864357,"size":1,"distinct_size":1,"ref":"refs/heads/bugfix/alert-api-typeerror","head":"6ccbc02c8e4b01d5e8235c849c7b1f65da8fa825","before":"db5a678509133366ffcc412dd73e17f0e763770d","commits":[{"sha":"6ccbc02c8e4b01d5e8235c849c7b1f65da8fa825","author":{"name":"Morten Brekkevold","email":"1bca271bd8f3d43f258adf84da867cd89415bdfa@uninett.no"},"message":"drop all crazy filters when a single alert is selected by its primary key\n\nThe plain /alert API returns a list of only unresolved alerts, which may be a\ntiny subset of the entire alert history. The filtering system surrounding the\nAPI was all written with this taken into account, and adds lots of default\nfilters that need to be removed using query parameters.\n\nThese filters are still active when the client requests a single specific\nAlertHistory entry by its primary key, which is just ridiculous (in reality,\nthe entire API endpoint should be reworked).\n\nThis stuff all worked poorly together under newer Django Request Framework\nversions, so this makes sure we do not apply our other filtering magic when\nrequesting a specific single alert by its primary key.","distinct":true,"url":"https://api.github.com/repos/lunkwill42/nav/commits/6ccbc02c8e4b01d5e8235c849c7b1f65da8fa825"}]}
{"actor":{"display_login":"lunkwill42"}}