Merge branch 'exercism:main' into implement-error-handling-exercise

Author: A-O-Emmanuel

.github/workflows/ci.js.yml

@@ -13,7 +13,7 @@ jobs:
     runs-on: ubuntu-24.04
 
     steps:
-      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683
+      - uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8
       - name: Enable corepack to fix https://github.com/actions/setup-node/pull/901
         run: corepack enable pnpm
 
@@ -37,7 +37,7 @@ jobs:
         node-version: [22.x]
 
     steps:
-      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683
+      - uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8
       - name: Enable corepack to fix https://github.com/actions/setup-node/pull/901
         run: corepack enable pnpm
 

.github/workflows/codeql.yml

@@ -29,7 +29,7 @@ jobs:
 
     steps:
       - name: Checkout repository
-        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683
+        uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8
 
       # Initializes the CodeQL tools for scanning.
       - name: Initialize CodeQL

.github/workflows/pr.ci.js.yml

@@ -11,7 +11,7 @@ jobs:
 
     steps:
       - name: Checkout PR
-        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683
+        uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8
         with:
           fetch-depth: ${{ github.event_name == 'pull_request' && 2 || 0 }}
 
@@ -48,7 +48,7 @@ jobs:
 
     steps:
       - name: Checkout PR
-        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683
+        uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8
         with:
           fetch-depth: ${{ github.event_name == 'pull_request' && 2 || 0 }}
 

.github/workflows/verify-code-formatting.yml

@@ -10,7 +10,7 @@ jobs:
     runs-on: ubuntu-24.04
     steps:
       - name: 'Checkout code'
-        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683
+        uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8
 
       - name: 'Verify formatting of all files'
         run: ./bin/check-formatting.sh

concepts/callbacks/about.md

@@ -81,7 +81,6 @@ You see this pattern often when dealing with asynchronous functions to assist wi
 Common `Array` functions use callback functions to define their behaviour:
 
 - `Array.prototype.forEach`:
-
   - Accepts a callback, which applies the callback to each element of an array.
 
     ```javascript
@@ -92,7 +91,6 @@ Common `Array` functions use callback functions to define their behaviour:
     ```
 
 - `Array.prototype.map`
-
   - Accepts a callback, which applies the callback to each element of an array using the result to create a new array.
 
     ```javascript
@@ -103,7 +101,6 @@ Common `Array` functions use callback functions to define their behaviour:
     ```
 
 - `Array.prototype.reduce`
-
   - Accepts a callback, which applies the callback to each element of an array, passing the result forward to the next invocation.
 
     ```javascript

concepts/closures/about.md

@@ -18,7 +18,6 @@ The name _closure_ is historically derived from [_λ-calculus_][wiki-lambda-calc
 ## Reasons to use closures in JavaScript
 
 1. Data Privacy / Data Encapsulation
-
    - Unlike other languages, in 2020, there was no way to specify _private_ variables. So closures can be used to effectively emulate _private_ variables (there was a proposal to introduce private variable notation, which might have become standard by the time you read this).
 
    ```javascript
@@ -37,7 +36,6 @@ The name _closure_ is historically derived from [_λ-calculus_][wiki-lambda-calc
    ```
 
 2. Partial Application
-
    - Functions may return functions, and when a returned function uses the argument of the function that created it, this is an example of using a closure to perform partial application. Sometimes this is called _currying_ a function.
 
    ```javascript

concepts/closures/introduction.md

@@ -18,7 +18,7 @@ twoDozen;
 // => Uncaught ReferenceError: twoDozen is not defined
 ```
 
-Except for braces `{}`, functions (and classes) als create new scopes, which can _enclose_ values:
+Except for braces `{}`, functions (and classes) also create new scopes, which can _enclose_ values:
 
 ```javascript
 const dozen = 12;

exercises/concept/amusement-park/.meta/design.md

@@ -32,26 +32,22 @@ This exercise could benefit from the following rules in the [analyzer][analyzer]
 The comment types mentioned below only serve as a proposal.
 
 1. `createVisitor`
-
    - `actionable`: If the student used a helper variable, give feedback that the result can be returned directly.
    - `celebratory`: If the student used classes, celebrate but let them know it is not necessary throughout this exercise.
    - `informative`: If the student did not use the short-hand notation but wrote `name: name` etc instead, let them know how to shorten that.
      The solution should be accepted nevertheless.
 
 2. `revokeTicket`
-
    - `essential`: Check the ticketId field is not deleted and re-added.
    - `celebratory`: If they used a method on a visitor class, celebrate but let them know it is not necessary for this exercise.
 
 3. `ticketStatus`
-
    - `essential`: Using a type switch should be discouraged since it is confusing to read because of the `typeof null === 'object'` quirk.
    - `informative`: If the student did not use early returns, maybe let them know about this alternative.
    - `celebratory`: Congratulate if the student used a template string for the "sold" case
    - `celebratory`: Congratulate if the student used a `value` helper variable.
 
 4. `simpleTicketStatus`
-
    - `essential`: Check `??` was used and not an if-statement or something else.
    - `actionable`: If the student used a helper variable, give feedback that the result can be returned directly.
 

exercises/concept/bird-watcher/.docs/instructions.md

@@ -16,7 +16,7 @@ To practice, use a `for` loop to solve each of the tasks below.
 Let us start analyzing the data by getting a high-level view.
 Find out how many birds you counted in total since you started your logs.
 
-Implement a function `totalBirdCount` that accepts an array that contains the bird count per day.
+Implement a function `totalBirdCount` that accepts an array-like object that contains the bird count per day.
 It should return the total number of birds that you counted.
 
 ```javascript
@@ -29,7 +29,7 @@ totalBirdCount(birdsPerDay);
 
 Now that you got a general feel for your bird count numbers, you want to make a more fine-grained analysis.
 
-Implement a function `birdsInWeek` that accepts an array of bird counts per day and a week number.
+Implement a function `birdsInWeek` that accepts an array-like object of bird counts per day and a week number.
 It returns the total number of birds that you counted in that specific week.
 You can assume weeks are always tracked completely.
 
@@ -46,7 +46,7 @@ You figured out that this bird always spent every second day in your garden.
 You do not know exactly where it was in between those days but definitely not in your garden.
 Your bird watcher intuition also tells you that the bird was in your garden on the first day that you tracked in your list.
 
-Given this new information, write a function `fixBirdCountLog` that takes an array of birds counted per day as an argument. It should correct the counting mistake and return the modified array.
+Given this new information, write a function `fixBirdCountLog` that takes an array-like object of birds counted per day as an argument. It should correct the counting mistake by modifying the given array.
 
 ```javascript
 birdsPerDay = [2, 5, 0, 7, 4, 1];

exercises/concept/bird-watcher/.meta/design.md

@@ -36,19 +36,16 @@ This exercise could benefit from the following rules in the [analyzer][analyzer]
 For all tasks check that the student actually used a for loop.
 
 1. `totalBirdCount`
-
    - Verify that the condition is written with `< x.length` instead of `<= y.length -1`.
    - Check whether a shorthand assignment `+=` was used to increase the sum (non-essential feedback).
    - Verify the total was properly initialized with `0` instead of e.g. `null`
    - Verify the increment operator was used in loop header step
 
 2. `birdsInWeek`
-
    - Verify a helper variable was used instead of duplicating the calculation in the initialization and condition of the loop
    - Other checks should be the same as for `totalBirdCount`
 
 3. `fixBirdCountLog`
-
    - Check whether a shorthand assignment `+=` was used to increase the loop counter (non-essential feedback)
    - Check whether the increment operator was used in the loop body