issue_comments
7 rows where "created_at" is on date 2019-05-02 sorted by author_association
This data as json, CSV (advanced)
Suggested facets: user, updated_at (date)
id | html_url | issue_url | node_id | user | created_at | updated_at | author_association ▼ | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
488595724 | https://github.com/simonw/datasette/pull/432#issuecomment-488595724 | https://api.github.com/repos/simonw/datasette/issues/432 | MDEyOklzc3VlQ29tbWVudDQ4ODU5NTcyNA== | russss 45057 | 2019-05-02T08:50:53Z | 2019-05-02T08:50:53Z | CONTRIBUTOR | > Can I pull those needs out of the Facet class somehow? I was thinking that it might be handy for datasette to have a request object which wraps the Sanic Request. This could include the datasette-specific querystring decoding and the `special_args` parsing from TableView.data. This would mean that we could expose the request object to plugin hooks without coupling them to Sanic. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Refactor facets to a class and new plugin, refs #427 432893491 | |
488528111 | https://github.com/simonw/datasette/issues/419#issuecomment-488528111 | https://api.github.com/repos/simonw/datasette/issues/419 | MDEyOklzc3VlQ29tbWVudDQ4ODUyODExMQ== | simonw 9599 | 2019-05-02T01:14:58Z | 2019-05-02T01:14:58Z | OWNER | I just closed #420 - all of the places in the codebase that were using `.inspect()` should have been eliminated. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Default to opening files in mutable mode, special option for immutable files 421551434 | |
488554835 | https://github.com/simonw/datasette/issues/438#issuecomment-488554835 | https://api.github.com/repos/simonw/datasette/issues/438 | MDEyOklzc3VlQ29tbWVudDQ4ODU1NDgzNQ== | simonw 9599 | 2019-05-02T05:09:18Z | 2019-05-02T05:09:18Z | OWNER | https://docs.pytest.org/en/latest/example/simple.html#detect-if-running-from-within-a-pytest-run | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Plugins are loaded when running pytest 438200529 | |
488555399 | https://github.com/simonw/datasette/issues/431#issuecomment-488555399 | https://api.github.com/repos/simonw/datasette/issues/431 | MDEyOklzc3VlQ29tbWVudDQ4ODU1NTM5OQ== | simonw 9599 | 2019-05-02T05:13:54Z | 2019-05-02T05:13:54Z | OWNER | Datasette master now treats databases as readonly but NOT immutable. This means you can make changes to those databases from another process and those changes will be instantly reflected in the Datasette interface. As such, reloading on database change is no longer necessary. Closing this ticket. | {"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Datasette doesn't reload when database file changes 432870248 | |
488558896 | https://github.com/simonw/datasette/issues/422#issuecomment-488558896 | https://api.github.com/repos/simonw/datasette/issues/422 | MDEyOklzc3VlQ29tbWVudDQ4ODU1ODg5Ng== | simonw 9599 | 2019-05-02T05:43:11Z | 2019-05-02T05:43:11Z | OWNER | I'm doing this with time limits right now, which I think is good enough for the moment. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Figure out what to do about table counts in a mutable world 423316403 | |
488564761 | https://github.com/simonw/datasette/issues/427#issuecomment-488564761 | https://api.github.com/repos/simonw/datasette/issues/427 | MDEyOklzc3VlQ29tbWVudDQ4ODU2NDc2MQ== | simonw 9599 | 2019-05-02T06:24:49Z | 2019-05-03T00:07:16Z | OWNER | https://github.com/simonw/datasette/compare/facet-refactor-2 is almost ready to merge now. The remaining things to do are listed as TODOs there: - [x] Ensure facet is not suggested if it is already active - [x] Don't allow facets to be hidden if they were configured in metadata.json | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | New design for facet abstraction, including querystring and metadata.json 431800286 | |
488564891 | https://github.com/simonw/datasette/issues/427#issuecomment-488564891 | https://api.github.com/repos/simonw/datasette/issues/427 | MDEyOklzc3VlQ29tbWVudDQ4ODU2NDg5MQ== | simonw 9599 | 2019-05-02T06:25:41Z | 2019-05-02T06:25:41Z | OWNER | It would be neat to ship at least one additional face with this work - probably either `ArrayFacet` or `DateFacet`. I think `ArrayFacet` because it demonstrates the only-if-json1-enabled functionality. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | New design for facet abstraction, including querystring and metadata.json 431800286 |
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]);
reactions 2 ✖