{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":779371895,"defaultBranch":"main","name":"pypeeringmanager","ownerLogin":"Netnod","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2024-03-29T17:24:14.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/17453615?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1711733578.0","currentOid":""},"activityList":{"items":[{"before":null,"after":"dc5da1973a8a3290144cc0535f6af4afc967b614","ref":"refs/heads/fix_model_response","pushedAt":"2024-03-29T17:32:58.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"emil-palm","name":"Emil Palm","path":"/emil-palm","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/103286?s=80&v=4"},"commit":{"message":"This fixes that pypeeringmanager always returned a pynetbox.core.response.Record instead of the given model.\n\nThe issue is that pynetbox.core.app calls `_set_model` and that method uses a hardcoded reference to pynetbox.core.App instead of giving the possibility to subclass app and provide your own models as pypeeringmanager is doing. This commit fixes that.","shortMessageHtmlLink":"This fixes that pypeeringmanager always returned a pynetbox.core.resp…"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEItuHIQA","startCursor":null,"endCursor":null}},"title":"Activity · Netnod/pypeeringmanager"}