issue_comments
5 rows where author_association = "OWNER" and "updated_at" is on date 2018-08-11 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date)
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
412299013 | https://github.com/simonw/datasette/issues/185#issuecomment-412299013 | https://api.github.com/repos/simonw/datasette/issues/185 | MDEyOklzc3VlQ29tbWVudDQxMjI5OTAxMw== | simonw 9599 | 2018-08-11T20:14:54Z | 2018-08-11T20:14:54Z | OWNER | I've been worrying about how this one relates to #260 - I'd like to validate metadata (to help protect against people e.g. misspelling I think the solution is to introduce a metadata key called
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Metadata should be a nested arbitrary KV store 299760684 | |
412291437 | https://github.com/simonw/datasette/issues/238#issuecomment-412291437 | https://api.github.com/repos/simonw/datasette/issues/238 | MDEyOklzc3VlQ29tbWVudDQxMjI5MTQzNw== | simonw 9599 | 2018-08-11T17:55:26Z | 2018-08-11T18:02:48Z | OWNER | On further thought, I'd much rather implement this using some kind of metadata plugin hook - see #357 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
External metadata.json 317714268 | |
412291395 | https://github.com/simonw/datasette/issues/231#issuecomment-412291395 | https://api.github.com/repos/simonw/datasette/issues/231 | MDEyOklzc3VlQ29tbWVudDQxMjI5MTM5NQ== | simonw 9599 | 2018-08-11T17:54:41Z | 2018-08-11T17:54:41Z | OWNER | I'm going to separate the issue of enabling and disabling plugins from the existence of the
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
metadata.json support for plugin configuration options 316323336 | |
412291327 | https://github.com/simonw/datasette/issues/188#issuecomment-412291327 | https://api.github.com/repos/simonw/datasette/issues/188 | MDEyOklzc3VlQ29tbWVudDQxMjI5MTMyNw== | simonw 9599 | 2018-08-11T17:53:17Z | 2018-08-11T17:53:17Z | OWNER | Potential problem: the existing
This doesn't make sense for metadata that is bundled with a specific database - there's no point in having the Calling such an embedded file |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Ability to bundle metadata and templates inside the SQLite file 309047460 | |
412290986 | https://github.com/simonw/datasette/issues/174#issuecomment-412290986 | https://api.github.com/repos/simonw/datasette/issues/174 | MDEyOklzc3VlQ29tbWVudDQxMjI5MDk4Ng== | simonw 9599 | 2018-08-11T17:46:51Z | 2018-08-11T17:46:51Z | OWNER | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
License/Source in footer should inherit from top level 281197863 |
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 5