github/datasette
1
0
Fork 0
mirror of https://github.com/simonw/datasette.git synced 2025-12-10 16:51:24 +01:00
Code Issues Projects Releases Packages Wiki Activity

Fixed some broken reference links on upgrade guide

Browse source
This commit is contained in:
Simon Willison 2025-11-03 14:34:29 -08:00
commit b3b8c5831b
2 changed files with 14 additions and 14 deletions
Download patch file Download diff file Expand all files Collapse all files

4
docs/upgrade-1.0a20.md
View file

@ -2,10 +2,10 @@
orphan: true orphan: true
--- ---
(upgrade_guide_v1_a20)=
# Datasette 1.0a20 plugin upgrade guide # Datasette 1.0a20 plugin upgrade guide
(upgrade_guide_v1_a20)=
<!-- START UPGRADE 1.0a20 --> <!-- START UPGRADE 1.0a20 -->
Datasette 1.0a20 makes some breaking changes to Datasette's permission system. Plugins need to be updated if they use **any of the following**: Datasette 1.0a20 makes some breaking changes to Datasette's permission system. Plugins need to be updated if they use **any of the following**:

24
docs/upgrade_guide.md
View file

@ -4,7 +4,7 @@
(upgrade_guide_v1)= (upgrade_guide_v1)=
## Datasette 0.X -> 1.0 ## Datasette 0.X -> 1.0
This section reviews breaking changes Datasette ``1.0`` has when upgrading from a ``0.XX`` version. For new features that ``1.0`` offers, see the :ref:`changelog`. This section reviews breaking changes Datasette ``1.0`` has when upgrading from a ``0.XX`` version. For new features that ``1.0`` offers, see the {ref}`changelog`.
(upgrade_guide_v1_sql_queries)= (upgrade_guide_v1_sql_queries)=
### New URL for SQL queries ### New URL for SQL queries
@ -37,7 +37,7 @@ Metadata was completely revamped for Datasette 1.0. There are a number of relate
(upgrade_guide_v1_metadata_split)= (upgrade_guide_v1_metadata_split)=
#### ``metadata.yaml`` split into ``datasette.yaml`` #### ``metadata.yaml`` split into ``datasette.yaml``
Before Datasette 1.0, the ``metadata.yaml`` file became a kitchen sink if a mix of metadata, configuration, and settings. Now ``metadata.yaml`` is strictly for metadata (ex title and descriptions of database and tables, licensing info, etc). Other settings have been moved to a ``datasette.yml`` configuration file, described in :ref:`configuration`. Before Datasette 1.0, the ``metadata.yaml`` file became a kitchen sink if a mix of metadata, configuration, and settings. Now ``metadata.yaml`` is strictly for metadata (ex title and descriptions of database and tables, licensing info, etc). Other settings have been moved to a ``datasette.yml`` configuration file, described in {ref}`configuration`.
To start Datasette with both metadata and configuration files, run it like this: To start Datasette with both metadata and configuration files, run it like this:
@ -85,14 +85,14 @@ def get_metadata(datasette, key, database, table):
pass pass
``` ```
Instead, plugins are encouraged to interact directly with Datasette's in-memory metadata tables in SQLite using the following methods on the :ref:`internals_datasette`: Instead, plugins are encouraged to interact directly with Datasette's in-memory metadata tables in SQLite using the following methods on the {ref}`internals_datasette`:
- :ref:`get_instance_metadata() <datasette_get_instance_metadata>` and :ref:`set_instance_metadata() <datasette_set_instance_metadata>` - {ref}`get_instance_metadata() <datasette_get_instance_metadata>` and {ref}`set_instance_metadata() <datasette_set_instance_metadata>`
- :ref:`get_database_metadata() <datasette_get_database_metadata>` and :ref:`set_database_metadata() <datasette_set_database_metadata>` - {ref}`get_database_metadata() <datasette_get_database_metadata>` and {ref}`set_database_metadata() <datasette_set_database_metadata>`
- :ref:`get_resource_metadata() <datasette_get_resource_metadata>` and :ref:`set_resource_metadata() <datasette_set_resource_metadata>` - {ref}`get_resource_metadata() <datasette_get_resource_metadata>` and {ref}`set_resource_metadata() <datasette_set_resource_metadata>`
- :ref:`get_column_metadata() <datasette_get_column_metadata>` and :ref:`set_column_metadata() <datasette_set_column_metadata>` - {ref}`get_column_metadata() <datasette_get_column_metadata>` and {ref}`set_column_metadata() <datasette_set_column_metadata>`
A plugin that stores or calculates its own metadata can implement the :ref:`plugin_hook_startup` hook to populate those items on startup, and then call those methods while it is running to persist any new metadata changes. A plugin that stores or calculates its own metadata can implement the {ref}`plugin_hook_startup` hook to populate those items on startup, and then call those methods while it is running to persist any new metadata changes.
(upgrade_guide_v1_metadata_json_removed)= (upgrade_guide_v1_metadata_json_removed)=
#### The ``/metadata.json`` endpoint has been removed #### The ``/metadata.json`` endpoint has been removed
@ -106,10 +106,10 @@ As of Datasette ``1.0a14``, the ``.metadata()`` method on the Datasette Python A
Instead, one should use the following methods on a Datasette class: Instead, one should use the following methods on a Datasette class:
- :ref:`get_instance_metadata() <datasette_get_instance_metadata>` - {ref}`get_instance_metadata() <datasette_get_instance_metadata>`
- :ref:`get_database_metadata() <datasette_get_database_metadata>` - {ref}`get_database_metadata() <datasette_get_database_metadata>`
- :ref:`get_resource_metadata() <datasette_get_resource_metadata>` - {ref}`get_resource_metadata() <datasette_get_resource_metadata>`
- :ref:`get_column_metadata() <datasette_get_column_metadata>` - {ref}`get_column_metadata() <datasette_get_column_metadata>`
```{include} upgrade-1.0a20.md ```{include} upgrade-1.0a20.md
:heading-offset: 1 :heading-offset: 1