From f0c6c9e1301cd3cfbaace88f9fcda749e4844b7d Mon Sep 17 00:00:00 2001 From: gavinleroy Date: Thu, 12 Sep 2024 21:47:09 -0400 Subject: [PATCH] Note on bottom up view obligations --- book/src/trait-debugging-101.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/book/src/trait-debugging-101.md b/book/src/trait-debugging-101.md index 02936f0..3e3a513 100644 --- a/book/src/trait-debugging-101.md +++ b/book/src/trait-debugging-101.md @@ -155,6 +155,10 @@ Argus sorts the failing leaves in the Bottom-Up view by which are "most-likely" The above demonstrates that Argus identifies `Res: IntoResponse` as a root cause of the overall failure in addition to the second failure: `LoginAttempt: FromRequestParts<_, _>`. The note icon in the Bottom-Up view indicates that the two failures must be resolved together if you want to us the function as a handler. +It's always important to **read** and **understand** the failing obligation(s) that Argus presents first in the Bottom Up view. These errors are the *leaves* of the search tree, in other words, the *root cause* of the overall error; if you satisfy these bounds, then the root bound will also be satisfied. + +If additional failing bounds are present under "Other failures," you need to only resolve a single set of these failures. Argus shows you the set it believes was your intent, but as the developer with intent double check for yourself that it makes sense. +