issues

Table actions

7 rows where milestone = 5234079 and type = "issue" sorted by updated_at descending

✖
✖
✖

✎ View and edit SQL

This data as json, CSV (advanced)

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

type 1

  • issue · 7 ✖

state 1

repo 1

id node_id number title user state locked assignee milestone comments created_at updated_at ▲ closed_at author_association pull_request body repo type active_lock_reason performed_via_github_app reactions draft state_reason
396212021 MDU6SXNzdWUzOTYyMTIwMjE= 394 base_url configuration setting simonw 9599 closed 0   Datasette 0.39 5234079 27 2019-01-05T23:48:48Z 2020-06-11T09:15:20Z 2020-03-25T00:18:45Z OWNER  

I've identified a couple of use-cases for running Datasette in a way that over-rides the default way that internal URLs are generated.

  1. Running behind a reverse proxy. I tried running Datasette behind a proxy and found that some of the generated internal links incorrectly referenced http://127.0.0.1:8001/fixtures/... - when they should have been referencing http://my-host.my-domain.com/fixtures/... - this is a problem both for links within the HTML interface but also for the toggle_url keys returned in the JSON as part of the facets datastructure.
  2. I would like it to be possible to host a Datasette instance at e.g. https://www.mynewspaper.com/interactives/2018/election-results/ - either through careful HTTP proxying or, once Datasette has been ported to ASGI, by mounting a Datasette ASGI instance deep within an existing set of URL routes.

I'm going to add a url_prefix configuration option. This will default to "", which means Datasette will behave as it does at the moment - it will use / for most URL prefixes in the HTML version, and an absolute URL derived from the incoming Host header for URLs that are returned as part of the JSON output.

If url_prefix is set to another value (either a full URL or a path) then this path will be appended to all generated URLs.

 datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/394/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
585390482 MDU6SXNzdWU1ODUzOTA0ODI= 702 Option in metadata.json to set default sort order for a table simonw 9599 closed 0   Datasette 0.39 5234079 5 2020-03-21T00:19:56Z 2020-03-25T04:19:36Z 2020-03-22T02:40:35Z OWNER  

If you access the table page without any ?_sort or ?_sort_desc arguments it currently defaults to order by primary key - would be neat to be able to change that.

 datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/702/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
587398703 MDU6SXNzdWU1ODczOTg3MDM= 711 Release notes for Datasette 0.39 simonw 9599 closed 0   Datasette 0.39 5234079 2 2020-03-25T02:31:13Z 2020-03-25T04:06:55Z 2020-03-25T04:06:55Z OWNER  

Then I can ship it.

 datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/711/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
585626199 MDU6SXNzdWU1ODU2MjYxOTk= 705 latest.datasette.io is no longer updating simonw 9599 closed 0   Datasette 0.39 5234079 15 2020-03-22T01:59:30Z 2020-03-25T02:30:24Z 2020-03-25T02:30:24Z OWNER   datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/705/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
583970196 MDU6SXNzdWU1ODM5NzAxOTY= 701 Search box CSS doesn't look great on OS X Safari simonw 9599 closed 0   Datasette 0.39 5234079 3 2020-03-18T20:00:52Z 2020-03-24T22:57:18Z 2020-03-24T22:57:18Z OWNER  

datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/701/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
585597329 MDU6SXNzdWU1ODU1OTczMjk= 704 Add datasette-publish-fly to Datasette Publish documentation simonw 9599 closed 0   Datasette 0.39 5234079 1 2020-03-21T22:25:10Z 2020-03-24T22:39:09Z 2020-03-24T22:39:09Z OWNER  

It's a cool example of a plugin that provides a new publish provider - worth mentioning on https://datasette.readthedocs.io/en/stable/publish.html

 datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/704/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
587314002 MDU6SXNzdWU1ODczMTQwMDI= 709 Each plugin hook should link to example plugins built with it simonw 9599 closed 0   Datasette 0.39 5234079 1 2020-03-24T22:18:48Z 2020-03-24T22:30:10Z 2020-03-24T22:29:43Z OWNER  
datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/709/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed

Advanced export

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

CSV options: 

CREATE TABLE [issues] (
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [number] INTEGER,
   [title] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [state] TEXT,
   [locked] INTEGER,
   [assignee] INTEGER REFERENCES [users]([id]),
   [milestone] INTEGER REFERENCES [milestones]([id]),
   [comments] INTEGER,
   [created_at] TEXT,
   [updated_at] TEXT,
   [closed_at] TEXT,
   [author_association] TEXT,
   [pull_request] TEXT,
   [body] TEXT,
   [repo] INTEGER REFERENCES [repos]([id]),
   [type] TEXT
, [active_lock_reason] TEXT, [performed_via_github_app] TEXT, [reactions] TEXT, [draft] INTEGER, [state_reason] TEXT);
CREATE INDEX [idx_issues_repo]
                ON [issues] ([repo]);
CREATE INDEX [idx_issues_milestone]
                ON [issues] ([milestone]);
CREATE INDEX [idx_issues_assignee]
                ON [issues] ([assignee]);
CREATE INDEX [idx_issues_user]
                ON [issues] ([user]);