From de611a9c643db89aa743d7accfef5a3b64fcd57b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?L=C3=A9o=20Valais?= Date: Tue, 7 Jan 2025 18:45:07 +0100 Subject: [PATCH] Update content/docs/reference/design-docs/editoast-errors/_index.en.md Co-authored-by: Jean SIMARD --- content/docs/reference/design-docs/editoast-errors/_index.en.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/reference/design-docs/editoast-errors/_index.en.md b/content/docs/reference/design-docs/editoast-errors/_index.en.md index a2d3a0753..4ca437ef6 100644 --- a/content/docs/reference/design-docs/editoast-errors/_index.en.md +++ b/content/docs/reference/design-docs/editoast-errors/_index.en.md @@ -339,7 +339,7 @@ Eventually, when all errors are converted and views errors are attached to their 1. Remove `trait EditoastError`, `derive(EditoastError)` and `struct InternalError` (at least its former version as the name may be reused in a different scope) 2. Adapt the frontend error keys collection script to look for errors in the OpenAPI routes response section instead of `components/schemas` -5. (Out of scope) Discuss with the frontend the level of visibility about internal errors we want to give the user +3. (Out of scope) Discuss with the frontend the level of visibility about internal errors we want to give the user ### Rejected ideas