pull_requests: 663836965
This data as json
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 663836965 | MDExOlB1bGxSZXF1ZXN0NjYzODM2OTY1 | 1368 | closed | 0 | DRAFT: A new plugin hook for dynamic metadata | 2670795 | Note that this is a WORK IN PROGRESS! This PR adds the following plugin hook: get_metadata( datasette=self, key=key, database=database, table=table, fallback=fallback ) This gets called when we're building our metdata for the rest of the system to use. Datasette merges whatever the plugins return with any local metadata (from metadata.yml/yaml/json) allowing for a live-editable dynamic Datasette. __A major design consideration is this: should Datasette perform the metadata merge? Or should Datasette allow plugins to perform any modifications themselves?__ As a security precation, local meta is *not* overwritable by plugin hooks. The workflow for transitioning to live-meta would be to load the plugin with the full metadata.yaml and save. Then remove the parts of the metadata that you want to be able to change from the file. I have a WIP dynamic configuration plugin here, for reference: https://github.com/next-LI/datasette-live-config/ | 2021-06-07T18:56:00Z | 2021-06-26T22:24:54Z | 2021-06-26T22:24:54Z | 2021-06-26T22:24:54Z | baf986c871708c01ca183be760995cf306ba21bf | 0 | 84fe80cb94ad2d6d7d88f6dec94b6c317fbe20d9 | 953a64467d78bca29fe6cc18bdb2baa7848e53ff | CONTRIBUTOR | 107914493 | https://github.com/simonw/datasette/pull/1368 |
Links from other tables
- 0 rows from pull_requests_id in labels_pull_requests