issue_comments

Table actions

4 rows where issue = 634917088 and "updated_at" is on date 2020-06-09 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

  • Example permissions plugin · 4 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
641026230 https://github.com/simonw/datasette/issues/818#issuecomment-641026230 https://api.github.com/repos/simonw/datasette/issues/818 MDEyOklzc3VlQ29tbWVudDY0MTAyNjIzMA== simonw 9599 2020-06-09T04:50:24Z 2020-06-09T04:50:24Z OWNER

I'm dropping this from the 0.44 milestone.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Example permissions plugin 634917088  
641013524 https://github.com/simonw/datasette/issues/818#issuecomment-641013524 https://api.github.com/repos/simonw/datasette/issues/818 MDEyOklzc3VlQ29tbWVudDY0MTAxMzUyNA== simonw 9599 2020-06-09T03:57:38Z 2020-06-09T04:00:24Z OWNER

Problem with that is it's more of a actor_from_request opportunity than permission_allowed. You could use actor_from_request to authenticate API clients from their Authorization: header, then use the regular "allow" blocks in metadata.json to actually assign their permissions.

The most interesting permissions plugin would be one that implements permissions against some kind of database schema, hence allowing admins to edit permissions through writable canned queries.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Example permissions plugin 634917088  
641009744 https://github.com/simonw/datasette/issues/818#issuecomment-641009744 https://api.github.com/repos/simonw/datasette/issues/818 MDEyOklzc3VlQ29tbWVudDY0MTAwOTc0NA== simonw 9599 2020-06-09T03:43:18Z 2020-06-09T03:43:18Z OWNER

datasette-auth-bearer perhaps?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Example permissions plugin 634917088  
641009442 https://github.com/simonw/datasette/issues/818#issuecomment-641009442 https://api.github.com/repos/simonw/datasette/issues/818 MDEyOklzc3VlQ29tbWVudDY0MTAwOTQ0Mg== simonw 9599 2020-06-09T03:41:55Z 2020-06-09T03:41:55Z OWNER

I want to build a plugin that does Authorization: Bearer xxx API key authentication.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Example permissions plugin 634917088  

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