issue_comments: 1314615592
This data as json
| html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | issue | performed_via_github_app |
|---|---|---|---|---|---|---|---|---|---|---|---|
| https://github.com/simonw/datasette/issues/1875#issuecomment-1314615592 | https://api.github.com/repos/simonw/datasette/issues/1875 | 1314615592 | IC_kwDOBm6k_c5OW3Eo | 9599 | 2022-11-15T01:04:28Z | 2022-11-15T01:04:28Z | OWNER | Worth noting this bit in RFC 7807: > The fictional problem type here defines the "errors" extension, an > array that describes the details of each validation error. Each > member is an object containing "detail" to describe the issue, and > "pointer" to locate the problem within the request's content using a > JSON Pointer [JSON-POINTER]. So the list of `"errors"` with JSON Pointer isn't technically part of the spec, it's an imaginary extension. It fits what I need to do though, so I'm inclined to stick with it anyway. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | 1430797211 |