diff --git a/content/01-Getting-Started/02-Nesting-Objects/instructions.mdx b/content/01-Getting-Started/02-Nesting-Objects/instructions.mdx index 6f85bf6..ec14f3d 100644 --- a/content/01-Getting-Started/02-Nesting-Objects/instructions.mdx +++ b/content/01-Getting-Started/02-Nesting-Objects/instructions.mdx @@ -40,4 +40,4 @@ To nest objects within objects, you can define a property as an `object` with it ``` -Now, try to modify the `name` property on the side editor to add `firstName`, `lastName`, and `middleName` with type `string`. \ No newline at end of file +Now, try to modify the `name` property on the to add `firstName`, `lastName`, and `middleName` with type `string`. \ No newline at end of file diff --git a/content/01-Getting-Started/03-Required-Properties/instructions.mdx b/content/01-Getting-Started/03-Required-Properties/instructions.mdx index e4b3955..a854057 100644 --- a/content/01-Getting-Started/03-Required-Properties/instructions.mdx +++ b/content/01-Getting-Started/03-Required-Properties/instructions.mdx @@ -41,4 +41,4 @@ if those properties are not present, the JSON data is considered invalid. ``` -Now, try to modify the `name` property on the side editor and add `firstName` and `lastName` as **required** properties. \ No newline at end of file +Now, try to modify the `name` property on the and add `firstName` and `lastName` as **required** properties. \ No newline at end of file diff --git a/content/01-Getting-Started/04-Enumerated-Values/instructions.mdx b/content/01-Getting-Started/04-Enumerated-Values/instructions.mdx index 7700be4..47328c4 100644 --- a/content/01-Getting-Started/04-Enumerated-Values/instructions.mdx +++ b/content/01-Getting-Started/04-Enumerated-Values/instructions.mdx @@ -35,7 +35,7 @@ To define the enumerated values in _JSON Schema_, use the `enum` keyword. ``` -Now, try to modify the `hobbies` property on the side editor with `enum` constrain to only allow `reading`, `writing`, and `painting` values. +Now, try to modify the `hobbies` property on the with `enum` constrain to only allow `reading`, `writing`, and `painting` values. Values defined in `enum` are case-sensitive. diff --git a/content/01-Getting-Started/05-Arrays/instructions.mdx b/content/01-Getting-Started/05-Arrays/instructions.mdx index 3da1380..2749edc 100644 --- a/content/01-Getting-Started/05-Arrays/instructions.mdx +++ b/content/01-Getting-Started/05-Arrays/instructions.mdx @@ -34,5 +34,5 @@ You can use the `items` keyword to define the *schema* of the array elements. Th ``` -Now, try to modify the `hobbies` property on the side editor and convert it to an **array of strings**. +Now, try to modify the `hobbies` property on the and convert it to an **array of strings**. diff --git a/content/01-Getting-Started/06-Array-of-Objects/instructions.mdx b/content/01-Getting-Started/06-Array-of-Objects/instructions.mdx index 9873fec..a16df75 100644 --- a/content/01-Getting-Started/06-Array-of-Objects/instructions.mdx +++ b/content/01-Getting-Started/06-Array-of-Objects/instructions.mdx @@ -44,5 +44,5 @@ Start by defining `skills` as an array. set the `items` keyword to define the ty } } ``` -Now, try to modify the `skills` property in the schema given to you in the editor, and make it an array of objects with `name` and `level` properties. +Now, try to modify the `skills` property in the schema given to you in the , and make it an array of objects with `name` and `level` properties. diff --git a/content/02-Primitive-Types/01-Constraining-String-Length/instructions.mdx b/content/02-Primitive-Types/01-Constraining-String-Length/instructions.mdx index a7d6324..1f52ad1 100644 --- a/content/02-Primitive-Types/01-Constraining-String-Length/instructions.mdx +++ b/content/02-Primitive-Types/01-Constraining-String-Length/instructions.mdx @@ -39,7 +39,7 @@ In *JSON Schema*, you can use the `minLength` and `maxLength` keywords to define } ``` -Now, try to modify the `postalCode` and `phoneNumber` fields in the side editor with the below constraints in mind. +Now, try to modify the `postalCode` and `phoneNumber` fields in the with the below constraints in mind. **Constraints:** - The `postalCode` should be a string with a length of **exactly 6** characters. diff --git a/content/02-Primitive-Types/02-Regular-Expressions-in-Strings/instructions.mdx b/content/02-Primitive-Types/02-Regular-Expressions-in-Strings/instructions.mdx index a5058c8..f847d6b 100644 --- a/content/02-Primitive-Types/02-Regular-Expressions-in-Strings/instructions.mdx +++ b/content/02-Primitive-Types/02-Regular-Expressions-in-Strings/instructions.mdx @@ -43,7 +43,7 @@ Let's break down the regular expression `^[0-9]{6}$`: - `{6}` specifies that the previous pattern should be repeated exactly 6 times. - `$` asserts the end of the string. -Now, try to modify the `postalCode`, `phoneNumber` and `countryCode` fields in the side editor with the below constraints in mind. +Now, try to modify the `postalCode`, `phoneNumber` and `countryCode` fields in the with the below constraints in mind. **Constraints:** - The `postalCode` should be a string with a length of **exactly 6** characters and should **contain only digits.** diff --git a/content/02-Primitive-Types/03-Constraining-Number/instructions.mdx b/content/02-Primitive-Types/03-Constraining-Number/instructions.mdx index 592f7fc..2aa78c2 100644 --- a/content/02-Primitive-Types/03-Constraining-Number/instructions.mdx +++ b/content/02-Primitive-Types/03-Constraining-Number/instructions.mdx @@ -62,7 +62,7 @@ To apply constraints on number values, you can use the following keywords: } ``` -now try to modify the `age` and `dateOfBirth` properties in the side editor with the constraints mentioned below: +now try to modify the `age` and `dateOfBirth` properties in the with the constraints mentioned below: - `age` should be between 18 and 60 - `dateOfBirth.year` should be between 1964 and 2024 diff --git a/content/02-Primitive-Types/04-Exclusively-Constraining-Number/instructions.mdx b/content/02-Primitive-Types/04-Exclusively-Constraining-Number/instructions.mdx index c558382..7851a34 100644 --- a/content/02-Primitive-Types/04-Exclusively-Constraining-Number/instructions.mdx +++ b/content/02-Primitive-Types/04-Exclusively-Constraining-Number/instructions.mdx @@ -28,7 +28,7 @@ To apply exclusive constraints on number values, you can use the following keywo - x < `exclusiveMaximum` -now try to add the `age` and `salary` properties in the schema given on the side editor with the constraints mentioned below using `exclusiveMinimum` and `exclusiveMaximum` keywords: +now try to add the `age` and `salary` properties in the schema given on the with the constraints mentioned below using `exclusiveMinimum` and `exclusiveMaximum` keywords: - `age` should be **greater than 18** and **less than 60** - `salary` should be **greater than 30000** and **less than 80000** diff --git a/content/02-Primitive-Types/05-Multiple-of-a-Number/instructions.mdx b/content/02-Primitive-Types/05-Multiple-of-a-Number/instructions.mdx index da46fe2..7aeaecb 100644 --- a/content/02-Primitive-Types/05-Multiple-of-a-Number/instructions.mdx +++ b/content/02-Primitive-Types/05-Multiple-of-a-Number/instructions.mdx @@ -30,7 +30,7 @@ The `multipleOf` keyword is used to define a number which is a multiple of anoth } ``` -Now, try to modify the JSON object such that `hourlyWage` property follows the given constraints. +Now, try to modify the JSON schema given in the such that `hourlyWage` property follows the given constraints. **Constraints** - `hourlyWage` should be a **multiple of 0.25** diff --git a/content/02-Primitive-Types/06-Decimal-Numbers/instructions.mdx b/content/02-Primitive-Types/06-Decimal-Numbers/instructions.mdx index 71c0eaa..e7717b7 100644 --- a/content/02-Primitive-Types/06-Decimal-Numbers/instructions.mdx +++ b/content/02-Primitive-Types/06-Decimal-Numbers/instructions.mdx @@ -18,7 +18,7 @@ Consider a new property, `performanceRating`. } ``` -Now, Try to modify the `performanceRating` property on the side editor to accept decimal numbers with **minimum** value as **0** and **maximum** value as **5**. +Now, Try to modify the `performanceRating` property on the to accept decimal numbers with **minimum** value as **0** and **maximum** value as **5**. Also modify the `age` property to accept only `integer` values.
(There is no need to set the minimum and maximum values for the `age` property.) \ No newline at end of file diff --git a/content/02-Primitive-Types/07-Enumerated-Values-II/instructions.mdx b/content/02-Primitive-Types/07-Enumerated-Values-II/instructions.mdx index 5393d11..5356bf9 100644 --- a/content/02-Primitive-Types/07-Enumerated-Values-II/instructions.mdx +++ b/content/02-Primitive-Types/07-Enumerated-Values-II/instructions.mdx @@ -25,4 +25,4 @@ Let's say you want to restrict the `performanceRating` to only a few specific va } ``` -Now, modify the `performanceRating` property on the side editor to accept only the values 1, 2, 3, 4, 5, and null. \ No newline at end of file +Now, modify the `performanceRating` property on the to accept only the values 1, 2, 3, 4, 5, and null. \ No newline at end of file diff --git a/content/02-Primitive-Types/08-Defining-Constant-Values/instructions.mdx b/content/02-Primitive-Types/08-Defining-Constant-Values/instructions.mdx index b887571..ccbab3d 100644 --- a/content/02-Primitive-Types/08-Defining-Constant-Values/instructions.mdx +++ b/content/02-Primitive-Types/08-Defining-Constant-Values/instructions.mdx @@ -30,7 +30,7 @@ The `const` keyword is used to define a single constant value for a property. Th } ``` -Now, try to add a new property `companyName` in the JSON object such that it should have a constant value `MyCompany`. +Now, try to add a new property `companyName` in the JSON schema in such that it should have a constant value `MyCompany`. Just for practice, we will also **set the age to a constant value of 25**. diff --git a/content/02-Primitive-Types/09-Combining-Types/instructions.mdx b/content/02-Primitive-Types/09-Combining-Types/instructions.mdx index e6ec941..2cdafe6 100644 --- a/content/02-Primitive-Types/09-Combining-Types/instructions.mdx +++ b/content/02-Primitive-Types/09-Combining-Types/instructions.mdx @@ -51,4 +51,4 @@ In _JSON Schema_, you can define multiple types by passing **an array of types** -Now, try to modify the `hasAgreedToTerms` property on the side editor to accept both `boolean` and `null` values. \ No newline at end of file +Now, try to modify the `hasAgreedToTerms` property on the to accept both `boolean` and `null` values. \ No newline at end of file diff --git a/content/03-Objects/01-Pattern-Properties/instructions.mdx b/content/03-Objects/01-Pattern-Properties/instructions.mdx index b8ad889..39f095b 100644 --- a/content/03-Objects/01-Pattern-Properties/instructions.mdx +++ b/content/03-Objects/01-Pattern-Properties/instructions.mdx @@ -37,7 +37,7 @@ We will define a property that starts with `DEPT-` followed by department number } ``` -Now, modify the schema provided in the editor on the right to permit `DEPT-*` properties. Additionally, ensure that the values for `DEPT-*` properties are constrained to be in **all capital letters.** +Now, modify the schema provided in the on the right to permit `DEPT-*` properties. Additionally, ensure that the values for `DEPT-*` properties are constrained to be in **all capital letters.** > **Hint:** Use the `patternProperties` keyword to define the pattern for the property name and `pattern` keyword to define the pattern for the property value. you can set `pattern` to `^[A-Z]+$` to match all capital letters. diff --git a/content/03-Objects/02-Additional-Properties/instructions.mdx b/content/03-Objects/02-Additional-Properties/instructions.mdx index 032b122..3ffdd2f 100644 --- a/content/03-Objects/02-Additional-Properties/instructions.mdx +++ b/content/03-Objects/02-Additional-Properties/instructions.mdx @@ -50,4 +50,4 @@ You can also set `additionalProperties` to a schema to define the schema for the The above schema will allow only `name` and `age` properties in the object. If any other property is present in the object, it should be of type `string`. -Now, try to modify the schema provided in the editor on the right to allow any additional properties of type `integer`. \ No newline at end of file +Now, try to modify the schema provided in the on the right to allow any additional properties of type `integer`. \ No newline at end of file diff --git a/content/03-Objects/03-Constraining-Number-of-Properties/instructions.mdx b/content/03-Objects/03-Constraining-Number-of-Properties/instructions.mdx index 7232193..b07d2bf 100644 --- a/content/03-Objects/03-Constraining-Number-of-Properties/instructions.mdx +++ b/content/03-Objects/03-Constraining-Number-of-Properties/instructions.mdx @@ -26,7 +26,7 @@ Let's add a new property `contactMethods` in the employee object and set constra } ``` -Now, add the `minProperties` and `maxProperties` keywords to the schema on the side editor to set the minimum and maximum number of properties in the `contactMethods` object. +Now, add the `minProperties` and `maxProperties` keywords to the schema on the to set the minimum and maximum number of properties in the `contactMethods` object. In the `contactMethods` object, set the minimum number of properties to `2` and the maximum number of properties to `5`. diff --git a/content/03-Objects/04-Applying-Schema-to-Property-Names/instructions.mdx b/content/03-Objects/04-Applying-Schema-to-Property-Names/instructions.mdx index a00bca1..d737fee 100644 --- a/content/03-Objects/04-Applying-Schema-to-Property-Names/instructions.mdx +++ b/content/03-Objects/04-Applying-Schema-to-Property-Names/instructions.mdx @@ -24,7 +24,7 @@ We want to ensure that each property names are written in capital letters. We ca } ``` -You are given an empty object schema in the right-hand editor. Modify it ensure that it follows the below constraints: +You are given an empty object schema in the . Modify it ensure that it follows the below constraints: 1. The object should have at **least 2 properties**. 2. The **property names** should be written **in capital letters**, and should have **minimum length of 3 characters**. diff --git a/content/04-Arrays/01-Specifying-Length-of-an-Array/instructions.mdx b/content/04-Arrays/01-Specifying-Length-of-an-Array/instructions.mdx index 4a8c6a2..fc3d663 100644 --- a/content/04-Arrays/01-Specifying-Length-of-an-Array/instructions.mdx +++ b/content/04-Arrays/01-Specifying-Length-of-an-Array/instructions.mdx @@ -38,6 +38,6 @@ In *JSON Schema*, you can specify the minimum and maximum number of items in an } } ``` -Now, modify the `phones` property of the given schema on the side editor, and specify minimum items as `1` and maximum items as `3`. Additionally constrain the phone numbers to be in the format `xxx-xxx-xxxx`. +Now, modify the `phones` property of the given schema on the , and specify minimum items as `1` and maximum items as `3`. Additionally constrain the phone numbers to be in the format `xxx-xxx-xxxx`. > **Hint:** Use regular expression `^\\d{3}-\\d{3}-\\d{4}$` with `pattern` keyword to validate the phone number format. \ No newline at end of file diff --git a/content/04-Arrays/02-Unique-Items/instructions.mdx b/content/04-Arrays/02-Unique-Items/instructions.mdx index 9635ac4..f9b0f87 100644 --- a/content/04-Arrays/02-Unique-Items/instructions.mdx +++ b/content/04-Arrays/02-Unique-Items/instructions.mdx @@ -33,4 +33,4 @@ To ensure that the items in an array are unique, you can use the `uniqueItems` k } ``` -Now, try to modify the `phones` property in the schema given on the side editor to ensure that the phone numbers are unique. \ No newline at end of file +Now, try to modify the `phones` property in the schema given on the to ensure that the phone numbers are unique. \ No newline at end of file diff --git a/content/04-Arrays/03-Tuple-Validation/instructions.mdx b/content/04-Arrays/03-Tuple-Validation/instructions.mdx index f3a8668..acc955f 100644 --- a/content/04-Arrays/03-Tuple-Validation/instructions.mdx +++ b/content/04-Arrays/03-Tuple-Validation/instructions.mdx @@ -43,4 +43,4 @@ In such cases, you can use the `prefixItems` keyword to define the schema for ea The above schema defines an array in which, the first element should be an `integer` and the second element should be a `string`. -Now, try to modify the `address` property on the side editor, such that it follows the constraints mentioned above. \ No newline at end of file +Now, try to modify the `address` property on the , such that it follows the constraints mentioned above. \ No newline at end of file diff --git a/content/04-Arrays/04-Additional-Items-in-Tuples/instructions.mdx b/content/04-Arrays/04-Additional-Items-in-Tuples/instructions.mdx index b8f9feb..0c0373f 100644 --- a/content/04-Arrays/04-Additional-Items-in-Tuples/instructions.mdx +++ b/content/04-Arrays/04-Additional-Items-in-Tuples/instructions.mdx @@ -29,6 +29,6 @@ You can set the `items` keyword to `false` to disallow additional items in the t ``` -Now, try to modify the `address` property on the side editor, to allow **only string values as additional items** in the tuple array. +Now, try to modify the `address` property on the , to allow **only string values as additional items** in the tuple array. > **Hint:** add a *subschema* to the `items` keyword to define the schema for the additional items. \ No newline at end of file diff --git a/content/04-Arrays/05-Enumerated-Array-Items/instructions.mdx b/content/04-Arrays/05-Enumerated-Array-Items/instructions.mdx index 8cd2bc9..4ff5fce 100644 --- a/content/04-Arrays/05-Enumerated-Array-Items/instructions.mdx +++ b/content/04-Arrays/05-Enumerated-Array-Items/instructions.mdx @@ -31,7 +31,7 @@ now, we want to restrict the `relevantDepartments` property to only a few specif } ``` -Now, Let's try to add the `enum` keyword to the schema given in the side editor and restrict the `relevantDepartments` property to only the values `HR`, `Finance`, `IT`, and `Admin`. +Now, Let's try to add the `enum` keyword to the schema given in the and restrict the `relevantDepartments` property to only the values `HR`, `Finance`, `IT`, and `Admin`. Also, **each item in the array should be unique**. diff --git a/content/04-Arrays/06-Ensuring-Array-Content-With-Contains/instructions.mdx b/content/04-Arrays/06-Ensuring-Array-Content-With-Contains/instructions.mdx index ca5a451..10f34d1 100644 --- a/content/04-Arrays/06-Ensuring-Array-Content-With-Contains/instructions.mdx +++ b/content/04-Arrays/06-Ensuring-Array-Content-With-Contains/instructions.mdx @@ -34,6 +34,6 @@ Our employee document has a field called `skills`. } ``` -Now, we want to ensure that the `skills` array contains at least one element that is equal to `"JavaScript"`. modify the schema given to you in the side editor to apply this constrain. +Now, we want to ensure that the `skills` array contains at least one element that is equal to `"JavaScript"`. modify the schema given to you in the to apply this constrain. > **Hint:** Use the `const` keyword to specify JavaScript as the required element. \ No newline at end of file diff --git a/content/04-Arrays/07-minContains-and-maxContains/instructions.mdx b/content/04-Arrays/07-minContains-and-maxContains/instructions.mdx index 182a523..a88d07b 100644 --- a/content/04-Arrays/07-minContains-and-maxContains/instructions.mdx +++ b/content/04-Arrays/07-minContains-and-maxContains/instructions.mdx @@ -40,6 +40,6 @@ The following example demonstrates how to use the `minContains` and `maxContains } ``` -Our employee has field called worked hours. We want to ensure that the `workedHours` array contains **at least 2 elements** that are **greater than or equal to 8 and less than or equal 12**. Modify the schema given to you in the side editor to apply this constraint. +Our employee has field called worked hours. We want to ensure that the `workedHours` array contains **at least 2 elements** that are **greater than or equal to 8 and less than or equal 12**. Modify the schema given to you in the to apply this constraint. diff --git a/content/04-Arrays/08-Unevaluated-Items/instructions.mdx b/content/04-Arrays/08-Unevaluated-Items/instructions.mdx index c1f5cda..704d64f 100644 --- a/content/04-Arrays/08-Unevaluated-Items/instructions.mdx +++ b/content/04-Arrays/08-Unevaluated-Items/instructions.mdx @@ -47,7 +47,7 @@ In this case, first two items are evaluated by `prefixItems` and the remaining i } ``` -Modify the `skills` property of the given schema on the side editor such that, +Modify the `skills` property of the given schema on the such that, - First three elements can have only "HTML", "CSS" and "JavaScript" as values (in any order), not anything else. - The remaining elements are of type string. diff --git a/content/05-Conditional-Validation/01-Ensuring-Conditional-Property-Presence/instructions.mdx b/content/05-Conditional-Validation/01-Ensuring-Conditional-Property-Presence/instructions.mdx index f1f5aeb..646836c 100644 --- a/content/05-Conditional-Validation/01-Ensuring-Conditional-Property-Presence/instructions.mdx +++ b/content/05-Conditional-Validation/01-Ensuring-Conditional-Property-Presence/instructions.mdx @@ -63,4 +63,4 @@ In the above schema, the `age` property is required if the `name` property is pr } ``` -You are given a *Schema* for the above JSON document in the side editor. Update the schema to make sure that if the `creditCardNumber` property is present, then the `address` property must also be present. \ No newline at end of file +You are given a *Schema* for the above JSON document in the . Update the schema to make sure that if the `creditCardNumber` property is present, then the `address` property must also be present. \ No newline at end of file diff --git a/content/05-Conditional-Validation/02-Ensuring-Mutual-Dependency/instructions.mdx b/content/05-Conditional-Validation/02-Ensuring-Mutual-Dependency/instructions.mdx index 044b745..7cb0fc0 100644 --- a/content/05-Conditional-Validation/02-Ensuring-Mutual-Dependency/instructions.mdx +++ b/content/05-Conditional-Validation/02-Ensuring-Mutual-Dependency/instructions.mdx @@ -39,4 +39,4 @@ Similar to the previous lesson, we can use the `dependentRequired` keyword to en } ``` -You are given a *Schema* for the above JSON document in the side editor. Update the schema to make sure that `creditCardNumber` and `address` are mutually dependent. \ No newline at end of file +You are given a *Schema* for the above JSON document in the . Update the schema to make sure that `creditCardNumber` and `address` are mutually dependent. \ No newline at end of file diff --git a/content/05-Conditional-Validation/03-Conditionally-Apply-a-Subschema/instructions.mdx b/content/05-Conditional-Validation/03-Conditionally-Apply-a-Subschema/instructions.mdx index 930b1b6..272ff31 100644 --- a/content/05-Conditional-Validation/03-Conditionally-Apply-a-Subschema/instructions.mdx +++ b/content/05-Conditional-Validation/03-Conditionally-Apply-a-Subschema/instructions.mdx @@ -63,4 +63,4 @@ You can use the `dependentSchemas` keyword to enforce this condition. } ``` -You are given a *Schema* for the above JSON document in the side editor. Update the schema to make sure that if the `creditCardNumber` property is present, then the `address` property must also be present using the `dependentSchemas` keyword. \ No newline at end of file +You are given a *Schema* for the above JSON document in the . Update the schema to make sure that if the `creditCardNumber` property is present, then the `address` property must also be present using the `dependentSchemas` keyword. \ No newline at end of file diff --git a/content/05-Conditional-Validation/04-if-then-else/instructions.mdx b/content/05-Conditional-Validation/04-if-then-else/instructions.mdx index 9b60e9f..b5d8e95 100644 --- a/content/05-Conditional-Validation/04-if-then-else/instructions.mdx +++ b/content/05-Conditional-Validation/04-if-then-else/instructions.mdx @@ -50,7 +50,7 @@ You can use the `if-then-else` keyword to enforce this condition. } ``` -You are given the schema for the same JSON document in the side editor. Modify the schema to enforce the below condition: +You are given the schema for the same JSON document in the . Modify the schema to enforce the below condition: - **If** `isStudent` is true, **then** the `age` field must be present, **else** the `grade` field must be present. diff --git a/content/05-Conditional-Validation/05-implications/instructions.mdx b/content/05-Conditional-Validation/05-implications/instructions.mdx index 4100d5d..e11167d 100644 --- a/content/05-Conditional-Validation/05-implications/instructions.mdx +++ b/content/05-Conditional-Validation/05-implications/instructions.mdx @@ -45,6 +45,6 @@ You can use the `if-then` keyword to enforce this condition. } ``` -You are given the schema for the same JSON document in the side editor. Modify the schema to enforce the below condition: +You are given the schema for the same JSON document in the . Modify the schema to enforce the below condition: - **If** `isStudent` is true, **then** the `age` field must be present. diff --git a/content/06-Combining-Schemas/01-Reusing-and-Referencing-with-defs-and-ref/instructions.mdx b/content/06-Combining-Schemas/01-Reusing-and-Referencing-with-defs-and-ref/instructions.mdx index 9ab70f7..2f049a0 100644 --- a/content/06-Combining-Schemas/01-Reusing-and-Referencing-with-defs-and-ref/instructions.mdx +++ b/content/06-Combining-Schemas/01-Reusing-and-Referencing-with-defs-and-ref/instructions.mdx @@ -47,5 +47,5 @@ Using `$defs` and `$ref` can help make your JSON Schema more modular and maintai } } ``` -Define a *subschema* named `stringType` which is just `"type": "string"` and then reference it using `$ref` for the `properties` **firstName**, **middleName** and **lastName** +Define a *subschema* named `stringType` in the schema given in , which is just `"type": "string"` and then reference it using `$ref` for the `properties` **firstName**, **middleName** and **lastName** diff --git a/content/06-Combining-Schemas/02-id-and-schema/instructions.mdx b/content/06-Combining-Schemas/02-id-and-schema/instructions.mdx index bffc241..57ceeda 100644 --- a/content/06-Combining-Schemas/02-id-and-schema/instructions.mdx +++ b/content/06-Combining-Schemas/02-id-and-schema/instructions.mdx @@ -52,6 +52,6 @@ We have defined a simple schema as below. "type": "string" } ``` -Reference this schema in the `name` property using the `$ref` keyword in the schema given to you in the side editor. +Reference this schema in the `name` property using the `$ref` keyword in the schema given to you in the . diff --git a/content/06-Combining-Schemas/03-Valid-Against-allOf-the-Subschemas(AND)/instructions.mdx b/content/06-Combining-Schemas/03-Valid-Against-allOf-the-Subschemas(AND)/instructions.mdx index cb49b46..5543537 100644 --- a/content/06-Combining-Schemas/03-Valid-Against-allOf-the-Subschemas(AND)/instructions.mdx +++ b/content/06-Combining-Schemas/03-Valid-Against-allOf-the-Subschemas(AND)/instructions.mdx @@ -53,7 +53,7 @@ The above schema ensures that the `name` property is valid against both the `min } ``` -For the given JSON document, you are provided with a schema in the side editor. the schema has defined a subschemas `ageLimit`. +For the given JSON document, you are provided with a schema in the . the schema has defined a subschemas `ageLimit`. Your task is to: - Define a inline subschema that checks if the `age` is of type `integer` - Combine the `ageLimit` and the inline subschema using `allOf` in the `age` property. \ No newline at end of file diff --git a/content/06-Combining-Schemas/04-Valid-Against-oneOf-the-Subschemas(XOR)/instructions.mdx b/content/06-Combining-Schemas/04-Valid-Against-oneOf-the-Subschemas(XOR)/instructions.mdx index 9721e88..e97fe72 100644 --- a/content/06-Combining-Schemas/04-Valid-Against-oneOf-the-Subschemas(XOR)/instructions.mdx +++ b/content/06-Combining-Schemas/04-Valid-Against-oneOf-the-Subschemas(XOR)/instructions.mdx @@ -63,7 +63,7 @@ We will combine using `oneOf` and `required`, to ensure that only one of the pro } ``` -You are given a *Schema* for the above JSON document in the side editor. Using `oneOf` keyword, update schema to ensure that the `age` follows one of the below conditions: +You are given a *Schema* for the above JSON document in the . Using `oneOf` keyword, update schema to ensure that the `age` follows one of the below conditions: - Either between 18 and 60 (inclusive) or, - Greater then 65 (inclusive). diff --git a/content/06-Combining-Schemas/05-Valid-Against-anyOf-the-Subschemas(OR)/instructions.mdx b/content/06-Combining-Schemas/05-Valid-Against-anyOf-the-Subschemas(OR)/instructions.mdx index ecb9e40..c2ce5c9 100644 --- a/content/06-Combining-Schemas/05-Valid-Against-anyOf-the-Subschemas(OR)/instructions.mdx +++ b/content/06-Combining-Schemas/05-Valid-Against-anyOf-the-Subschemas(OR)/instructions.mdx @@ -47,7 +47,7 @@ Create a JSON schema that validates the following document. ``` -Modify the schema given to you in the side editor to ensure that the document is valid if +Modify the schema given to you in the to ensure that the document is valid if - It has either `salary` or `hourlyRate` property. - It has both `employeeType` and `salary` properties. diff --git a/content/06-Combining-Schemas/06-inverting-validation-with-not/instructions.mdx b/content/06-Combining-Schemas/06-inverting-validation-with-not/instructions.mdx index 36cf414..d5af042 100644 --- a/content/06-Combining-Schemas/06-inverting-validation-with-not/instructions.mdx +++ b/content/06-Combining-Schemas/06-inverting-validation-with-not/instructions.mdx @@ -44,6 +44,6 @@ We want the `age` to be greater then or equal to 18. but it should not be 21. We } ``` -Modify the schema given to you in the side editor to ensure that the document is valid if: +Modify the schema given to you in the to ensure that the document is valid if: - `status` is **not** `null`. diff --git a/content/06-Combining-Schemas/07-Recursive-Schemas/instructions.mdx b/content/06-Combining-Schemas/07-Recursive-Schemas/instructions.mdx index 4333a46..0532a74 100644 --- a/content/06-Combining-Schemas/07-Recursive-Schemas/instructions.mdx +++ b/content/06-Combining-Schemas/07-Recursive-Schemas/instructions.mdx @@ -67,7 +67,7 @@ In the above example, the `TreeNode` schema refers to itself in the `children` p } } ``` -You are given an incomplete JSON Schema in the right side editor. +You are given an incomplete JSON Schema in the right . Define the `next` schema using recursive schemas. here `next` is a linked list of values. > **Hint:** diff --git a/content/07-Miscellaneous/01-Extending-Closed-Schemas-with-unevaluatedProperties/instructions.mdx b/content/07-Miscellaneous/01-Extending-Closed-Schemas-with-unevaluatedProperties/instructions.mdx index 785f19b..264e3eb 100644 --- a/content/07-Miscellaneous/01-Extending-Closed-Schemas-with-unevaluatedProperties/instructions.mdx +++ b/content/07-Miscellaneous/01-Extending-Closed-Schemas-with-unevaluatedProperties/instructions.mdx @@ -60,5 +60,5 @@ The challenge we saw with `additionalProperties` can be solved using the `uneval ## Task -You are give the same schema in the text editor. Add `unevaluatedProperties` to the schema to allow the only `number` as an additional property. +You are give the same schema in the . Add `unevaluatedProperties` to the schema to allow the only `number` as an additional property. diff --git a/content/08-Annotating-JSON-Schemas/01-Title-and-Description/instructions.mdx b/content/08-Annotating-JSON-Schemas/01-Title-and-Description/instructions.mdx index 6650b7a..91df93b 100644 --- a/content/08-Annotating-JSON-Schemas/01-Title-and-Description/instructions.mdx +++ b/content/08-Annotating-JSON-Schemas/01-Title-and-Description/instructions.mdx @@ -30,4 +30,4 @@ Here's an example of a schema with a title and description: ``` # Task -Add `title` and `description` to the schema given to you in the side editor. You can use any title and description you like. \ No newline at end of file +Add `title` and `description` to the schema given to you in the . You can use any title and description you like. \ No newline at end of file diff --git a/content/08-Annotating-JSON-Schemas/02-deprecated-readOnly-and-writeOnly/instructions.mdx b/content/08-Annotating-JSON-Schemas/02-deprecated-readOnly-and-writeOnly/instructions.mdx index 102b9c8..bb8b232 100644 --- a/content/08-Annotating-JSON-Schemas/02-deprecated-readOnly-and-writeOnly/instructions.mdx +++ b/content/08-Annotating-JSON-Schemas/02-deprecated-readOnly-and-writeOnly/instructions.mdx @@ -60,7 +60,7 @@ Here, the `name` property is marked as `readOnly`, and the `age` property is mar } ``` -You are given schema of the above JSON object. +You are given schema of the above JSON object in . - Add `deprecated` keyword to the schema. - Add `readOnly` in the schema to the `name` property - Add `writeOnly` to the `age` property. diff --git a/content/08-Annotating-JSON-Schemas/03-comment-and-default/instructions.mdx b/content/08-Annotating-JSON-Schemas/03-comment-and-default/instructions.mdx index a7a0d76..0f76aff 100644 --- a/content/08-Annotating-JSON-Schemas/03-comment-and-default/instructions.mdx +++ b/content/08-Annotating-JSON-Schemas/03-comment-and-default/instructions.mdx @@ -40,6 +40,6 @@ You can set a default value for a property using the `default` keyword. The `def } ``` -You are given schema of the above JSON object. +You are given schema of the above JSON object in . - Add any comment to the `name` property. - Set any default value to the `age` property. \ No newline at end of file diff --git a/content/08-Annotating-JSON-Schemas/04-format-and-examples/instructions.mdx b/content/08-Annotating-JSON-Schemas/04-format-and-examples/instructions.mdx index cd1144a..25ce611 100644 --- a/content/08-Annotating-JSON-Schemas/04-format-and-examples/instructions.mdx +++ b/content/08-Annotating-JSON-Schemas/04-format-and-examples/instructions.mdx @@ -45,6 +45,6 @@ The `examples` keyword is used to provide an array of example values that are va } ``` -You are given a schema of the above JSON object in the side editor. +You are given a schema of the above JSON object in the . - Add a `format` to the `email` property. - Add `example` to the `email` property.