issues

Table actions

21 rows where milestone = 2949431, repo = 107914493 and type = "issue" sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: user, comments, author_association, body, created_at (date), updated_at (date), closed_at (date)

type 1

  • issue · 21 ✖

state 1

repo 1

  • datasette · 21 ✖
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
280013907 MDU6SXNzdWUyODAwMTM5MDc= 164 datasette skeleton command for kick-starting database and table metadata simonw 9599 closed 0   Custom templates edition 2949431 3 2017-12-07T06:13:28Z 2021-03-23T02:45:12Z 2017-12-07T06:20:45Z OWNER  

Generates an example metadata.json file populated with all of the databases and tables inspected from the specified databases.

 datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/164/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
275814941 MDU6SXNzdWUyNzU4MTQ5NDE= 141 datasette publish can fail if /tmp is on a different device jacobian 21148 closed 0   Custom templates edition 2949431 5 2017-11-21T18:28:05Z 2020-04-29T03:27:54Z 2017-12-08T16:06:36Z CONTRIBUTOR  

datasette publish uses hard links to avoid copying the db into a tmp directory. This can fail if /tmp is on another device, because hardlinks can't cross devices. You'll see something like this:

$ datasette publish heroku whatever.db ... OSError: [Errno 18] Invalid cross-device link: '/mnt/c/Users/jacob/c/datasette/whatever.db' -> '/tmp/tmpvxq2yof6/whatever.db' [In my case this is failing because I'm on a Windows machine, using WSL, so my code's on a different virtual filesystem from the Linux subsystem, Because Reasons.]

I'm not sure if it's possible to detect this (can you figure out which device /tmp is on?), or what the fallback should be (soft link? copy?).

 datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/141/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
278190321 MDU6SXNzdWUyNzgxOTAzMjE= 157 Teach "datasette publish" about custom template directories simonw 9599 closed 0   Custom templates edition 2949431 1 2017-11-30T16:44:57Z 2020-01-15T16:05:13Z 2017-12-09T18:28:54Z OWNER  

The following command should copy the custom templates into the deployment and ensure datasette serve correctly serves them:

datasette publish now mydb.db --template-dir=custom-templates/
datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/157/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
278208011 MDU6SXNzdWUyNzgyMDgwMTE= 160 Ability to bundle and serve additional static files simonw 9599 closed 0   Custom templates edition 2949431 8 2017-11-30T17:37:51Z 2019-02-02T00:58:20Z 2017-12-09T18:29:11Z OWNER  

Since we now have custom templates, we should support including custom static files with them as well. Maybe something like this:

datasette mydb.db --template-dir=templates/ --static-dir=static/

This should also be supported by datasette publish - see also #157

datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/160/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
276842536 MDU6SXNzdWUyNzY4NDI1MzY= 153 Ability to customize presentation of specific columns in HTML view ftrain 20264 closed 0   Custom templates edition 2949431 14 2017-11-26T17:46:11Z 2017-12-10T02:08:45Z 2017-12-07T06:17:33Z NONE  

This ties into https://github.com/simonw/datasette/issues/3 in some ways. It would be great to have some adaptability in the HTML views and to specific some columns as displaying in certain ways.

  • [x] 1. Auto-parsing URIs into in-browser links. Why? Lots of public data around cultural commons stuff links to a specific URL. This would be a great utility to turn on at the command line, just parse everything for URLs. Maybe they need to be underlined or represented in a different way than internal URLs.
  • [x] 2. Ability to identify a column as plain/preformatted text. Why? Was trying to import the Enron emails, the body collapses. Hard to read. These fields also tend to screw up the ability to scan a table view. If you knew it was text the system could set an overflow property on the relevant CSS, so you could still scan.
  • [x] 3. Ability to identify a column as HTML. Why? I want to spider some stuff and drop sections into SQLite, and just keep them as HTML.
 datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/153/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
280744309 MDU6SXNzdWUyODA3NDQzMDk= 169 Release v0.14 with templates and static files features simonw 9599 closed 0   Custom templates edition 2949431 1 2017-12-09T18:52:48Z 2017-12-10T02:04:56Z 2017-12-10T02:04:56Z OWNER   datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/169/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
280315352 MDU6SXNzdWUyODAzMTUzNTI= 167 Nasty bug: last column not being correctly displayed simonw 9599 closed 0   Custom templates edition 2949431 6 2017-12-07T23:23:46Z 2017-12-10T01:00:21Z 2017-12-10T01:00:20Z OWNER   datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/167/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
280745746 MDU6SXNzdWUyODA3NDU3NDY= 171 HTML comments specifying custom templates for page simonw 9599 closed 0   Custom templates edition 2949431 1 2017-12-09T19:11:13Z 2017-12-09T21:50:50Z 2017-12-09T21:48:03Z OWNER  

This would make the custom templating system self-documenting, and save people from having to figure out the right template names for customizing specific pages.

 datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/171/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
280745470 MDU6SXNzdWUyODA3NDU0NzA= 170 Custom template for named canned query simonw 9599 closed 0   Custom templates edition 2949431 3 2017-12-09T19:07:51Z 2017-12-09T21:35:30Z 2017-12-09T21:34:52Z OWNER  
datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/170/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
276873891 MDU6SXNzdWUyNzY4NzM4OTE= 154 Datasette CSS should include content hash in the URL simonw 9599 closed 0   Custom templates edition 2949431 3 2017-11-27T00:57:36Z 2017-12-09T03:10:23Z 2017-12-09T03:10:22Z OWNER  

When I deployed the latest version of datasette to https://fivethirtyeight.datasettes.com/ I noticed I was getting served stale CSS since it had been cached. Including the sha of he contents in its URL should fix that.

I can calculate this on server start.

 datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/154/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
280023225 MDU6SXNzdWUyODAwMjMyMjU= 166 Documentation for metadata.json and datasette skeleton simonw 9599 closed 0   Custom templates edition 2949431 1 2017-12-07T07:02:52Z 2017-12-07T17:20:35Z 2017-12-07T17:20:25Z OWNER  
datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/166/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
280014287 MDU6SXNzdWUyODAwMTQyODc= 165 metadata.json support for per-database and per-table information simonw 9599 closed 0   Custom templates edition 2949431 2 2017-12-07T06:15:34Z 2017-12-07T16:48:34Z 2017-12-07T16:47:29Z OWNER  

Every database and every table should be able to support the following optional metadata:

title
description
description_html
license
license_url
source
source_url

If description_html is provided it over-rides description and will be displayed unescaped.

 datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/165/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
278191223 MDU6SXNzdWUyNzgxOTEyMjM= 159 Come up with an elegant mechanism for per-row template customization simonw 9599 closed 0   Custom templates edition 2949431 0 2017-11-30T16:47:26Z 2017-12-07T06:12:27Z 2017-12-07T06:12:26Z OWNER  

It would be nice if customizing the display of an individual row in a custom table template was as simple as possible - refs #153

datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/159/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
278190981 MDU6SXNzdWUyNzgxOTA5ODE= 158 Ensure default templates are designed to be extended simonw 9599 closed 0   Custom templates edition 2949431 1 2017-11-30T16:46:41Z 2017-12-07T05:41:09Z 2017-12-07T05:41:08Z OWNER  

Since custom templates can do {% extends "default:table.html" %} the default templates should include sensible named {% block %} components designed to support common extension patterns. Since we already support {{ super() }} we may not have much if anything to add here.

 datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/158/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
277589569 MDU6SXNzdWUyNzc1ODk1Njk= 155 A primary key column that has foreign key restriction associated won't rendering label column wsxiaoys 388154 closed 0   Custom templates edition 2949431 4 2017-11-29T00:40:02Z 2017-12-07T05:39:53Z 2017-12-07T05:39:53Z NONE  
datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/155/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
276765070 MDU6SXNzdWUyNzY3NjUwNzA= 152 Incorrect display of rows page for tables with a primary key simonw 9599 closed 0   Custom templates edition 2949431 0 2017-11-25T17:29:54Z 2017-12-07T05:23:20Z 2017-12-07T05:23:19Z OWNER  

This is a regression. Here's the old version:

And here's the new, broken one:

https://parlgov-xtxlddmtiz.now.sh/parlgov-25f9855/party_family/1

The JSON output is the same for both - it's only the HTML representation that exhibits the bug.

 datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/152/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
279199916 MDU6SXNzdWUyNzkxOTk5MTY= 162 Link should not show up in the column selection dropdowns simonw 9599 closed 0   Custom templates edition 2949431 0 2017-12-05T00:19:04Z 2017-12-07T05:05:58Z 2017-12-07T05:05:58Z OWNER   datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/162/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
275179724 MDU6SXNzdWUyNzUxNzk3MjQ= 135 ?_search=x should work if used directly against a FTS virtual table simonw 9599 closed 0   Custom templates edition 2949431 3 2017-11-19T18:17:53Z 2017-12-07T04:54:41Z 2017-12-07T04:54:41Z OWNER   datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/135/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
267759136 MDU6SXNzdWUyNjc3NTkxMzY= 20 Config file with support for defining canned queries simonw 9599 closed 0 simonw 9599 Custom templates edition 2949431 9 2017-10-23T17:53:06Z 2017-12-05T19:05:35Z 2017-12-05T17:44:09Z OWNER  

Probably using YAML because then we get support for multiline strings:

bats:
  db: bats.sqlite3
  name: "Bat sightings"
  queries:
    specific_row: |
      select * from Bats
      where a = 1;
datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/20/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
278189708 MDU6SXNzdWUyNzgxODk3MDg= 156 Document CSS hooks and custom templates simonw 9599 closed 0   Custom templates edition 2949431 1 2017-11-30T16:43:15Z 2017-11-30T17:11:34Z 2017-11-30T17:10:58Z OWNER  

Documentation currently lives in commit messages on https://github.com/simonw/datasette/commit/8ab3a169d42d096f2c7979c6d3d7746618d30f0b and 3cd06729f457d690603b6060dc552b535517ab09

 datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/156/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
267523511 MDU6SXNzdWUyNjc1MjM1MTE= 12 Make it so you can override templates simonw 9599 closed 0   Custom templates edition 2949431 1 2017-10-23T02:25:35Z 2017-11-30T16:42:46Z 2017-11-30T16:38:34Z OWNER  

The app will ship with default templates but, just like with the Django admin, you will be able to override them using either explicit configuration settings or just by dropping in templates with certain file names.

Template inheritance should work here, both allowing you to override just the base template and allowing you to customize tiny bits of others.

 datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/12/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]);