From fafc32e0ea1adc95eea817af7273d4c47422b364 Mon Sep 17 00:00:00 2001 From: Bryan Newbold Date: Wed, 24 Nov 2021 15:48:42 -0800 Subject: codepsell fixes to notes --- notes/UNSORTED.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'notes/UNSORTED.txt') diff --git a/notes/UNSORTED.txt b/notes/UNSORTED.txt index 3960f5eb..850b54d0 100644 --- a/notes/UNSORTED.txt +++ b/notes/UNSORTED.txt @@ -3,7 +3,7 @@ Not allowed to PUT edits to the same entity in the same editgroup. If you want to update an edit, need to delete the old one first. The state depends only on the current entity state, not any redirect. This -means that if the target of a redirect is delted, the redirecting entity is +means that if the target of a redirect is deleted, the redirecting entity is still "redirect", not "deleted". Redirects-to-redirects are not allowed; this is enforced when the editgroup is @@ -31,7 +31,7 @@ redirects after some delay period. => it would not be too hard to update get_release_files to check for such redirects; could be handled by request flag? -`prev_rev` is naively set to the most-recent previous state. If the curent +`prev_rev` is naively set to the most-recent previous state. If the current state was deleted or a redirect, it is set to null. This parameter is not checked/enforced at edit accept time (but could be, and -- cgit v1.2.3