remote/datasette
1
0
Fork 0
mirror of https://github.com/simonw/datasette.git synced 2026-06-13 20:46:58 +02:00
Code Issues Projects Releases Packages Wiki Activity

Removed note from permission_resources_sql

Browse source 
Refs https://github.com/simonw/datasette/pull/2775/changes#r3408385197
This commit is contained in:
Simon Willison 2026-06-13 11:12:31 -07:00
commit ab19b0382b
1 changed files with 0 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/plugin_hooks.rst
View file

@ -1458,12 +1458,6 @@ to avoid conflicts with other plugins. The recommended convention is to prefix p
plugin's source name (e.g., ``myplugin_user_id``). The system reserves these parameter names:
``:actor``, ``:actor_id``, ``:action``, and ``:filter_parent``.
This hook may be called for many actions in rapid succession - for example
:ref:`datasette.allowed_many() <datasette_allowed_many>` gathers rules for every action in its batch
concurrently before table and database pages render their action menus. Hook implementations must not
assume that checks for different actions arrive one page-render apart, and expensive work (such as
network calls) should be cached independently of the ``action`` argument where possible.
You can also use return ``PermissionSQL.allow(reason="reason goes here")`` or ``PermissionSQL.deny(reason="reason goes here")`` as shortcuts for simple root-level allow or deny rules. These will create SQL snippets that look like this:
.. code-block:: sql