issue_comments
5 rows where reactions = "{"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}" and "updated_at" is on date 2018-06-05 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
user 1
- simonw 5
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
394894910 | https://github.com/simonw/datasette/issues/306#issuecomment-394894910 | https://api.github.com/repos/simonw/datasette/issues/306 | MDEyOklzc3VlQ29tbWVudDM5NDg5NDkxMA== | simonw 9599 | 2018-06-05T23:43:18Z | 2018-06-05T23:49:41Z | OWNER | I'm going to use a named tuple for the output. That way I can support either tuple destructing or explicit property access on the returned value. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Custom URL routing with independent tests 329661905 | |
394895267 | https://github.com/simonw/datasette/issues/306#issuecomment-394895267 | https://api.github.com/repos/simonw/datasette/issues/306 | MDEyOklzc3VlQ29tbWVudDM5NDg5NTI2Nw== | simonw 9599 | 2018-06-05T23:45:26Z | 2018-06-05T23:45:26Z | OWNER | To support a future where Datasette is an ASGI app that can be attached to a URL within a larger application the routing function should have the option to accept a path prefix which will then be automatically attached to any resulting redirects. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Custom URL routing with independent tests 329661905 | |
394894500 | https://github.com/simonw/datasette/issues/306#issuecomment-394894500 | https://api.github.com/repos/simonw/datasette/issues/306 | MDEyOklzc3VlQ29tbWVudDM5NDg5NDUwMA== | simonw 9599 | 2018-06-05T23:40:40Z | 2018-06-05T23:40:40Z | OWNER | Input: - function that says if a name is a valid database - Function that says if a table exists - URL Output: - view class - Arguments - Redirect (if it should redirect) |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Custom URL routing with independent tests 329661905 | |
392118755 | https://github.com/simonw/datasette/issues/272#issuecomment-392118755 | https://api.github.com/repos/simonw/datasette/issues/272 | MDEyOklzc3VlQ29tbWVudDM5MjExODc1NQ== | simonw 9599 | 2018-05-25T16:56:40Z | 2018-06-05T16:01:13Z | OWNER | Thinking about this further, maybe I should embrace ASGI turtles-all-the-way-down and teach each datasette view class to take a scope to the constructor and act entirely as an ASGI component. Would be a nice way of diving deep into ASGI and I can add utility helpers for things like querystring evaluation as I need them. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Port Datasette to ASGI 324188953 | |
394764713 | https://github.com/simonw/datasette/issues/272#issuecomment-394764713 | https://api.github.com/repos/simonw/datasette/issues/272 | MDEyOklzc3VlQ29tbWVudDM5NDc2NDcxMw== | simonw 9599 | 2018-06-05T15:58:54Z | 2018-06-05T16:00:40Z | OWNER | https://github.com/encode/uvicorn/blob/572b5fe6c811b63298d5350a06b664839624c860/uvicorn/run.py#L63 is how you start a Uvicorn server from code as opposed to the
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Port Datasette to ASGI 324188953 |
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]);
issue 2