issue_comments

Table actions

6 rows where issue = 678760988 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 1

issue 1

  • End-user documentation · 6 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
1061891851 https://github.com/simonw/datasette/issues/932#issuecomment-1061891851 https://api.github.com/repos/simonw/datasette/issues/932 IC_kwDOBm6k_c4_Sy8L simonw 9599 2022-03-08T15:20:48Z 2022-03-08T15:20:48Z OWNER

Made a start on this here: https://datasette.io/tutorials 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 End-user documentation 678760988  
1030940407 https://github.com/simonw/datasette/issues/932#issuecomment-1030940407 https://api.github.com/repos/simonw/datasette/issues/932 IC_kwDOBm6k_c49cub3 simonw 9599 2022-02-06T23:31:22Z 2022-02-06T23:31:22Z OWNER

Great argument for doing this from a conversation on Twitter about documentation-driven development:

Long ago, when the majority of commercial programs were desktop apps, I've read a very wise advice: The user manual should be written first, before even a single line if code.

https://twitter.com/b11c/status/1490466703175823362

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 End-user documentation 678760988  
674144798 https://github.com/simonw/datasette/issues/932#issuecomment-674144798 https://api.github.com/repos/simonw/datasette/issues/932 MDEyOklzc3VlQ29tbWVudDY3NDE0NDc5OA== simonw 9599 2020-08-14T16:02:24Z 2020-08-14T16:02:24Z OWNER

Things to go in here:

  • What is Datasette?
  • A database contains tables full of records. A table has rows and columns.
  • Understanding faceting
  • How to use the filter interface
  • How to export data
  • How to link to data
  • How to run SQL
 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 End-user documentation 678760988  
673735299 https://github.com/simonw/datasette/issues/932#issuecomment-673735299 https://api.github.com/repos/simonw/datasette/issues/932 MDEyOklzc3VlQ29tbWVudDY3MzczNTI5OQ== simonw 9599 2020-08-13T22:10:40Z 2020-08-13T22:11:06Z OWNER

Idea: plugins can provide their own user-facing documentation. Datasette can like to eg datasette.io/help?plugins=datasette-vega,datasette-cluster-map to get the user manual with extra sections for those plugins.

Or... link to ?url=datasette-url and the documentation site can hit /-/plugins.json to figure out what extra manual sections to display!

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 End-user documentation 678760988  
673734387 https://github.com/simonw/datasette/issues/932#issuecomment-673734387 https://api.github.com/repos/simonw/datasette/issues/932 MDEyOklzc3VlQ29tbWVudDY3MzczNDM4Nw== simonw 9599 2020-08-13T22:08:06Z 2020-08-13T22:08:06Z OWNER

One challenge: how does this interact with plugins?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 End-user documentation 678760988  
673733904 https://github.com/simonw/datasette/issues/932#issuecomment-673733904 https://api.github.com/repos/simonw/datasette/issues/932 MDEyOklzc3VlQ29tbWVudDY3MzczMzkwNA== simonw 9599 2020-08-13T22:06:50Z 2020-08-13T22:06:50Z OWNER

Title: Using Datasette. using.rst

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 End-user documentation 678760988  

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

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]);