Repository navigation
8.0.3
Added
Database::authorizeCreate()andDatabase::authorizeUpdate()take an optional resolver,
?callable $resolve = null, so a write staged after other writes is judged as it will run, after them.
$resolve(string $collection, string $id): ?Documentreturns a related document as the earlier staged writes leave
it: the document with its permissions (whether or not the caller can read it), an emptyDocumentwhen they delete
it, ornullwhen they leave it as stored. Every related-document lookup of the checks uses it: a document staged
for deletion is new to the write and needs create on its collection, a staged update or create is judged by its
staged permissions and links, and anullanswer reads the stored document as before. Without$resolvethe
checks are unchanged, and they still write nothing.
Full Changelog: 8.0.2...8.0.3