From bcfd107b56fb07dc24c7a91e9d3d322dee041bc8 Mon Sep 17 00:00:00 2001 From: Linh <62679553+dauinh@users.noreply.github.com> Date: Mon, 11 Mar 2024 14:40:15 -0400 Subject: [PATCH 1/8] Fix #198: Enhance generic keywords section with information on where they can be used (#430) * update annotation doc. fix typo in overview/what-is-json-schema * modify to alternative wording * remove "object" in wording --- pages/overview/what-is-jsonschema.md | 2 +- pages/understanding-json-schema/reference/annotations.md | 2 ++ 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/pages/overview/what-is-jsonschema.md b/pages/overview/what-is-jsonschema.md index 9da7957279..727084de3c 100644 --- a/pages/overview/what-is-jsonschema.md +++ b/pages/overview/what-is-jsonschema.md @@ -70,7 +70,7 @@ else: In the above code snippet, we are performing basic validation to check if the JSON object has the required fields. Since this is a relatively simpler data, this way of checking works for now. -To show the challenges of performing data validation without using JSON Schema, we can take this exmaple in Python: +To show the challenges of performing data validation without using JSON Schema, we can take this example in Python: ```python # Without JSON Schema diff --git a/pages/understanding-json-schema/reference/annotations.md b/pages/understanding-json-schema/reference/annotations.md index 9b848ac6ad..c9cd4caa65 100644 --- a/pages/understanding-json-schema/reference/annotations.md +++ b/pages/understanding-json-schema/reference/annotations.md @@ -8,6 +8,8 @@ validation, but are used to describe parts of a schema. None of these \"annotation\" keywords are required, but they are encouraged for good practice, and can make your schema \"self-documenting\". +Annotation keywords can be used in any schema or sub-schemas. Like other keywords, they may be used once. + The `title` and `description` keywords must be strings. A \"title\" will preferably be short, whereas a \"description\" will provide a more lengthy explanation about the purpose of the data described by the From c7e1f67f6c94fbe316132ed6cff4e8e59e875669 Mon Sep 17 00:00:00 2001 From: SATYAM KUMAR <106728045+satyam-x10@users.noreply.github.com> Date: Tue, 12 Mar 2024 14:53:59 +0530 Subject: [PATCH 2/8] Broken alignment in options menu #486 (#511) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * bug 🐛 Bug: Broken alignment in options menu when in mobile view #486 * Update Layout.tsx --- components/Layout.tsx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/components/Layout.tsx b/components/Layout.tsx index 4fe1914e2a..1d29183e85 100644 --- a/components/Layout.tsx +++ b/components/Layout.tsx @@ -215,7 +215,7 @@ const MobileNav = () => { const section = useContext(SectionContext); return ( -