pull_requests

Table actions

2 rows where "updated_at" is on date 2019-05-01

✎ View and edit SQL

This data as json, CSV (advanced)

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

id ▼ node_id number state locked title user body created_at updated_at closed_at merged_at merge_commit_sha assignee milestone draft head base author_association repo url merged_by auto_merge
274313625 MDExOlB1bGxSZXF1ZXN0Mjc0MzEzNjI1 439 closed 0 [WIP] Add primary key to the extra_body_script hook arguments russss 45057 This allows the row to be identified on row pages. The context here is that I want to access the row's data to plot it on a map. I considered passing the entire template context through to the hook function. This would expose the actual row data and potentially avoid a further fetch request in JS, but it does make the plugin API a lot more leaky. (At any rate, using the selected row data is tricky in my case because of Spatialite's infuriating custom binary representation...) 2019-04-29T10:08:23Z 2019-05-01T09:58:32Z 2019-05-01T09:58:30Z   b3cbcfef4d11d2741cf00861734d726a4730afe5     0 76b2c8fa406063b436155a7d8995e07b7e718c13 11b352b4d52fd02a422776edebb14f12e4994d3b CONTRIBUTOR datasette 107914493 https://github.com/simonw/datasette/pull/439    
274468836 MDExOlB1bGxSZXF1ZXN0Mjc0NDY4ODM2 441 closed 0 Add register_output_renderer hook russss 45057 This changeset refactors out the JSON renderer and then adds a hook and dispatcher system to allow custom output renderers to be registered. The CSV output renderer is untouched because supporting streaming renderers through this system would be significantly more complex, and probably not worthwhile. We can't simply allow hooks to be called at request time because we need a list of supported file extensions when the request is being routed in order to resolve ambiguous database/table names. So, renderers need to be registered at startup. I've tried to make this API independent of Sanic's request/response objects so that this can remain stable during the switch to ASGI. I'm using dictionaries to keep it simple and to make adding additional options in the future easy. Fixes #440 2019-04-29T18:03:21Z 2019-05-01T23:01:57Z 2019-05-01T23:01:57Z 2019-05-01T23:01:57Z cf406c075433882b656e340870adf7757976fa4c     0 c9f941f06eb0268841de49407725917c74a8a2dc 11b352b4d52fd02a422776edebb14f12e4994d3b CONTRIBUTOR datasette 107914493 https://github.com/simonw/datasette/pull/441    

Advanced export

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

CSV options: 

CREATE TABLE [pull_requests] (
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [number] INTEGER,
   [state] TEXT,
   [locked] INTEGER,
   [title] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [body] TEXT,
   [created_at] TEXT,
   [updated_at] TEXT,
   [closed_at] TEXT,
   [merged_at] TEXT,
   [merge_commit_sha] TEXT,
   [assignee] INTEGER REFERENCES [users]([id]),
   [milestone] INTEGER REFERENCES [milestones]([id]),
   [draft] INTEGER,
   [head] TEXT,
   [base] TEXT,
   [author_association] TEXT,
   [repo] INTEGER REFERENCES [repos]([id]),
   [url] TEXT,
   [merged_by] INTEGER REFERENCES [users]([id])
, [auto_merge] TEXT);
CREATE INDEX [idx_pull_requests_merged_by]
    ON [pull_requests] ([merged_by]);
CREATE INDEX [idx_pull_requests_repo]
    ON [pull_requests] ([repo]);
CREATE INDEX [idx_pull_requests_milestone]
    ON [pull_requests] ([milestone]);
CREATE INDEX [idx_pull_requests_assignee]
    ON [pull_requests] ([assignee]);
CREATE INDEX [idx_pull_requests_user]
    ON [pull_requests] ([user]);