issue_comments
8 rows where "created_at" is on date 2023-07-27 sorted by created_at
This data as json, CSV (advanced)
Suggested facets: issue_url, updated_at (date)
user 3
id | html_url | issue_url | node_id | user | created_at ▼ | updated_at | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
1652715823 | https://github.com/simonw/datasette/issues/2109#issuecomment-1652715823 | https://api.github.com/repos/simonw/datasette/issues/2109 | IC_kwDOBm6k_c5ignEv | simonw 9599 | 2023-07-27T00:17:04Z | 2023-07-27T00:18:07Z | OWNER | New decision: I had originally decided that the HTML view would just use data that could otherwise be extracted from the JSON view if you fed in enough extras. I've changed my mind. I'm OK with the HTML view getting a few bonus things available in its context, provided those are clearly documented for template authors. This should help avoid me having to make many changes to the templates themselves. HTML-specific stuff will be things like |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Plan for getting the new JSON format query views working 1822934563 | |
1652721111 | https://github.com/simonw/datasette/issues/2109#issuecomment-1652721111 | https://api.github.com/repos/simonw/datasette/issues/2109 | IC_kwDOBm6k_c5igoXX | simonw 9599 | 2023-07-27T00:23:28Z | 2023-07-27T00:23:37Z | OWNER | Once again I'm tempted to formalize the extra HTML context as a Here's an example of Hugging Face doing that: https://github.com/huggingface/transformers/blob/1689aea73346816b936b84932e12b774974e61a6/src/transformers/training_args.py#L622C1-L624 ```python from dataclasses import dataclass, field @dataclass class TrainingArguments: output_dir: str = field( metadata={"help": "The output directory where the model predictions and checkpoints will be written."}, ) ``` |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Plan for getting the new JSON format query views working 1822934563 | |
1652722208 | https://github.com/simonw/datasette/issues/2112#issuecomment-1652722208 | https://api.github.com/repos/simonw/datasette/issues/2112 | IC_kwDOBm6k_c5igoog | simonw 9599 | 2023-07-27T00:24:50Z | 2023-07-27T00:25:16Z | OWNER | I changed my mind, I'm not going to do this with a format hook. Also: https://github.com/simonw/datasette/issues/2109#issuecomment-1652715823 I've decided to let HTML have its own special context. I'm going to try formalizing that as a |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Build HTML version of /content?sql=... 1822938661 | |
1652723029 | https://github.com/simonw/datasette/issues/2112#issuecomment-1652723029 | https://api.github.com/repos/simonw/datasette/issues/2112 | IC_kwDOBm6k_c5igo1V | simonw 9599 | 2023-07-27T00:25:49Z | 2023-07-27T00:25:49Z | OWNER | Getting the query page working with all of the necessary HTML context variables is a slog. I uploaded
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Build HTML version of /content?sql=... 1822938661 | |
1652746185 | https://github.com/simonw/datasette/issues/2112#issuecomment-1652746185 | https://api.github.com/repos/simonw/datasette/issues/2112 | IC_kwDOBm6k_c5igufJ | simonw 9599 | 2023-07-27T00:46:37Z | 2023-07-27T00:46:37Z | OWNER | Got Claude to generate this code: ```python from dataclasses import dataclass, field @dataclass
class QueryContext:
database: str = field(metadata={"help": "The name of the database being queried"})
query: dict = field(metadata={"help": "The SQL query object containing the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Build HTML version of /content?sql=... 1822938661 | |
1652751140 | https://github.com/simonw/datasette/issues/2112#issuecomment-1652751140 | https://api.github.com/repos/simonw/datasette/issues/2112 | IC_kwDOBm6k_c5igvsk | simonw 9599 | 2023-07-27T00:52:53Z | 2023-07-27T00:52:53Z | OWNER | Maybe I teach |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Build HTML version of /content?sql=... 1822938661 | |
1653652665 | https://github.com/simonw/datasette/pull/2077#issuecomment-1653652665 | https://api.github.com/repos/simonw/datasette/issues/2077 | IC_kwDOBm6k_c5ikLy5 | dependabot[bot] 49699333 | 2023-07-27T13:40:52Z | 2023-07-27T13:40:52Z | CONTRIBUTOR | Superseded by #2121. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Bump furo from 2023.3.27 to 2023.5.20 1719759468 | |
1653666188 | https://github.com/simonw/datasette/pull/2121#issuecomment-1653666188 | https://api.github.com/repos/simonw/datasette/issues/2121 | IC_kwDOBm6k_c5ikPGM | codecov[bot] 22429695 | 2023-07-27T13:48:43Z | 2023-07-27T13:48:43Z | NONE | Codecov ReportPatch and project coverage have no change.
Additional details and impacted files```diff @@ Coverage Diff @@ ## main #2121 +/- ## ======================================= Coverage 92.38% 92.38% ======================================= Files 39 39 Lines 5803 5803 ======================================= Hits 5361 5361 Misses 442 442 ```:umbrella: View full report in Codecov by Sentry. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Bump furo from 2023.3.27 to 2023.7.26 1824399610 |
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 4