soften hints

Author: kentcdodds

exercises/01.objects/02.problem.property-access/README.mdx

@@ -19,12 +19,6 @@ user['name']
 2. Create a function that takes a product object and returns a formatted string
 3. Try accessing a property that doesn't exist (see the error!)
 
-💰 Function with object parameter:
-
-```ts
-function describe(product: { name: string; price: number }): string {
-	return `${product.name}: $${product.price}`
-}
-```
+💰 Define a function that accepts an object parameter and builds a string from it.
 
 📜 [MDN - Property accessors](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Property_accessors)

exercises/01.objects/02.problem.property-access/index.ts

@@ -14,7 +14,7 @@ const product = {
 
 // 🐨 Create a function `formatProduct` that takes a product object
 // and returns a string like "TypeScript Handbook - $29.99"
-// 💰 function formatProduct(p: { name: string; price: number }): string
+// 💰 The function should accept a product object and return a string
 
 // 🐨 Try uncommenting this line - what error do you see?
 // console.log(product.rating)

exercises/01.objects/03.problem.object-types/index.ts

@@ -5,7 +5,7 @@
 // - id: number
 // - title: string
 // - completed: boolean
-// 💰 type Task = { ... }
+// 💰 Define a Task type alias with the listed fields
 
 // 🐨 Create a `firstTask` and `secondTask` using the Task type
 // - firstTask: id 1, title "Write tests", completed false

exercises/01.objects/04.problem.optional-properties/README.mdx

@@ -19,15 +19,6 @@ const user: UserProfile = {
 2. Create users with and without the optional properties
 3. Safely access optional properties (check before using!)
 
-💰 Safely accessing optional properties:
-
-```ts
-if (user.bio !== undefined) {
-	console.log(user.bio.toUpperCase()) // Safe!
-}
-
-// Or use optional chaining:
-console.log(user.bio?.toUpperCase()) // Returns undefined if bio is undefined
-```
+💰 Check for missing values before using optional properties.
 
 📜 [TypeScript Handbook - Optional Properties](https://www.typescriptlang.org/docs/handbook/2/objects.html#optional-properties)

exercises/01.objects/04.problem.optional-properties/index.ts

@@ -23,8 +23,7 @@ const bob = {
 
 // 🐨 Create a function that displays user info
 // Handle the optional properties safely
-// 💰 Use optional chaining: user.bio?.toUpperCase()
-// 💰 Or check: if (user.bio !== undefined)
+// 💰 Safely handle missing optional values before using them
 
 // function displayUserInfo(user: { ... }): void {
 //   console.log(`Name: ${user.name}`)

exercises/01.objects/05.problem.dynamic-keys/README.mdx

@@ -1,13 +1,13 @@
 # Dynamic Object Keys
 
 👨‍💼 We need to model error pages where the property name isn't a valid
-identifier (like "404").
+identifier (like `status-404`).
 
 When the property name is stored in a variable, you can use a computed property
 name in an object literal:
 
 ```ts
-const key = '404'
+const key = 'status-404'
 const errorPages = {
 	[key]: '/not-found',
 }

exercises/01.objects/05.problem.dynamic-keys/index.ts

@@ -1,8 +1,8 @@
 // Error Pages
 // Computed property names in object literals
 
-const notFoundKey = '404'
-const serverErrorKey = '500'
+const notFoundKey = '404-status'
+const serverErrorKey = '500-status'
 
 const notFoundPath = '/not-found'
 const serverErrorPath = '/server-error'

exercises/01.objects/05.solution.dynamic-keys/README.mdx

@@ -1,12 +1,12 @@
 # Dynamic Object Keys
 
-👨‍💼 Nice work! You used computed property names to create keys like "404".
+👨‍💼 Nice work! You used computed property names to create keys like "404-status".
 
 🦉 The key idea is a **computed property name**, which lets you use a variable
 as the key when creating the object:
 
 ```ts
-const key = '404'
+const key = 'status-404'
 const errorPages = {
 	[key]: '/not-found',
 }

exercises/01.objects/05.solution.dynamic-keys/index.test.ts

@@ -11,13 +11,13 @@ await test('errorPages is exported', () => {
 
 await test('errorPages should include computed keys', () => {
 	assert.strictEqual(
-		solution.errorPages['404'],
+		solution.errorPages['404-status'],
 		'/not-found',
-		'🚨 errorPages["404"] should be "/not-found" - use the computed key',
+		'🚨 errorPages["404-status"] should be "/not-found" - use the computed key',
 	)
 	assert.strictEqual(
-		solution.errorPages['500'],
+		solution.errorPages['500-status'],
 		'/server-error',
-		'🚨 errorPages["500"] should be "/server-error" - use the computed key',
+		'🚨 errorPages["500-status"] should be "/server-error" - use the computed key',
 	)
 })

exercises/01.objects/05.solution.dynamic-keys/index.ts

@@ -1,8 +1,8 @@
 // Error Pages
 // Computed property names in object literals
 
-const notFoundKey = '404'
-const serverErrorKey = '500'
+const notFoundKey = '404-status'
+const serverErrorKey = '500-status'
 
 const notFoundPath = '/not-found'
 const serverErrorPath = '/server-error'