issue_comments
4 rows where issue = 1065431383
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
| id ▼ | html_url | issue_url | node_id | user | created_at | updated_at | author_association | body | reactions | issue | performed_via_github_app |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 981149039 | https://github.com/simonw/datasette/issues/1533#issuecomment-981149039 | https://api.github.com/repos/simonw/datasette/issues/1533 | IC_kwDOBm6k_c46eyVv | simonw 9599 | 2021-11-28T20:45:36Z | 2021-11-28T20:45:36Z | OWNER | I built an initial prototype of this in a branch: https://github.com/simonw/datasette/commit/e0a84691c2959f2d1d76948574c9c4a910c7556c - which exposed even more flaws in the way `TableView` is structured (adding custom HTTP headers to the response is way harder than it should be) which I should address in the refactor in #617. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Add `Link: rel="alternate"` header pointing to JSON for a table/query 1065431383 | |
| 1027633686 | https://github.com/simonw/datasette/issues/1533#issuecomment-1027633686 | https://api.github.com/repos/simonw/datasette/issues/1533 | IC_kwDOBm6k_c49QHIW | simonw 9599 | 2022-02-02T06:42:53Z | 2022-02-02T06:42:53Z | OWNER | I'm going to apply the hack, then fix it again in: - #1518 | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Add `Link: rel="alternate"` header pointing to JSON for a table/query 1065431383 | |
| 1027669851 | https://github.com/simonw/datasette/issues/1533#issuecomment-1027669851 | https://api.github.com/repos/simonw/datasette/issues/1533 | IC_kwDOBm6k_c49QP9b | simonw 9599 | 2022-02-02T07:51:57Z | 2022-02-02T07:51:57Z | OWNER | Documentation: https://docs.datasette.io/en/latest/json_api.html#discovering-the-json-for-a-page https://docs.datasette.io/en/latest/json_api.html top `--cors` section mentions the new `Access-Control-Expose-Headers: Link` header. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Add `Link: rel="alternate"` header pointing to JSON for a table/query 1065431383 | |
| 1027672617 | https://github.com/simonw/datasette/issues/1533#issuecomment-1027672617 | https://api.github.com/repos/simonw/datasette/issues/1533 | IC_kwDOBm6k_c49QQop | simonw 9599 | 2022-02-02T07:56:51Z | 2022-02-02T07:56:51Z | OWNER | Demos - these pages both have `<link rel=...` if you view source on them: - https://latest.datasette.io/fixtures/sortable - https://latest.datasette.io/fixtures/sortable/a,a And you can hit them with `curl` like so: ``` % curl -I 'https://latest.datasette.io/fixtures/sortable' HTTP/1.1 200 OK link: https://latest.datasette.io/fixtures/sortable.json; rel="alternate"; type="application/json+datasette" cache-control: max-age=5 referrer-policy: no-referrer access-control-allow-origin: * access-control-allow-headers: Authorization access-control-expose-headers: Link content-type: text/html; charset=utf-8 x-databases: _memory, _internal, fixtures, extra_database Date: Wed, 02 Feb 2022 07:56:17 GMT Server: Google Frontend Transfer-Encoding: chunked % curl -I 'https://latest.datasette.io/fixtures/sortable/a,a' HTTP/1.1 200 OK link: https://latest.datasette.io/fixtures/sortable/a,a.json; rel="alternate"; type="application/json+datasette" cache-control: max-age=5 referrer-policy: no-referrer access-control-allow-origin: * access-control-allow-headers: Authorization access-control-expose-headers: Link content-type: text/html; charset=utf-8 x-databases: _memory, _internal, fixtures, extra_database Date: Wed, 02 Feb 2022 07:56:24 GMT Server: Google Frontend Transfer-Encoding: chunked ``` | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Add `Link: rel="alternate"` header pointing to JSON for a table/query 1065431383 |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE [issue_comments] (
[html_url] TEXT,
[issue_url] TEXT,
[id] INTEGER PRIMARY KEY,
[node_id] TEXT,
[user] INTEGER REFERENCES [users]([id]),
[created_at] TEXT,
[updated_at] TEXT,
[author_association] TEXT,
[body] TEXT,
[reactions] TEXT,
[issue] INTEGER REFERENCES [issues]([id])
, [performed_via_github_app] TEXT);
CREATE INDEX [idx_issue_comments_issue]
ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
ON [issue_comments] ([user]);