@happychef/algorithm 1.3.0 → 1.4.0

package/.claude/settings.local.json

@@ -0,0 +1,16 @@
+{
+  "permissions": {
+    "allow": [
+      "Bash(cd \"H:\\\\UpWork\\\\Thaibault\\\\15-happy-algorithm\" && npx jest __tests__/verify2400.test.js --verbose 2>&1)",
+      "Bash(tail:*)",
+      "Bash(cd \"H:\\\\UpWork\\\\Thaibault\\\\15-happy-algorithm\" && npx jest __tests__/edgeCases.test.js --verbose 2>&1)",
+      "Bash(cd \"H:\\\\UpWork\\\\Thaibault\\\\15-happy-algorithm\" && node test/test_counter.js 2>&1)",
+      "Bash(cd \"H:\\\\UpWork\\\\Thaibault\\\\15-happy-algorithm\" && node test/test_dailyCount.js 2>&1)",
+      "Bash(cd \"H:\\\\UpWork\\\\Thaibault\\\\15-happy-algorithm\" && node test/test_exceptions.js 2>&1)",
+      "Bash(cd \"H:\\\\UpWork\\\\Thaibault\\\\15-happy-algorithm\" && node test/test_datesAvailable.js 2>&1)",
+      "Bash(cd \"H:\\\\UpWork\\\\Thaibault\\\\15-happy-algorithm\" && node test/test_mealTypeCount.js 2>&1)",
+      "Bash(cd \"H:\\\\UpWork\\\\Thaibault\\\\15-happy-algorithm\" && node test/test_isDateAvailable.js 2>&1)",
+      "Bash(grep:*)"
+    ]
+  }
+}

package/.github/workflows/ci-cd.yml

@@ -1,80 +1,80 @@
-name: CI/CD Pipeline
-
-on:
-  push:
-    branches:
-      - main
-  pull_request:
-    branches:
-      - main
-    types: [opened, synchronize, reopened]
-
-jobs:
-  publish:
-    name: Publish to NPM
-    runs-on: ubuntu-latest
-    if: github.ref == 'refs/heads/main' && github.event_name == 'push'
-
-    steps:
-      - name: Checkout code
-        uses: actions/checkout@v4
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: '20.x'
-          registry-url: 'https://registry.npmjs.org'
-          cache: 'npm'
-
-      - name: Install dependencies
-        run: npm ci
-
-      - name: Check if version changed
-        id: version-check
-        run: |
-          PACKAGE_VERSION=$(node -p "require('./package.json').version")
-          NPM_VERSION=$(npm view @happychef/algorithm version 2>/dev/null || echo "0.0.0")
-          echo "Package version: $PACKAGE_VERSION"
-          echo "NPM version: $NPM_VERSION"
-          if [ "$PACKAGE_VERSION" != "$NPM_VERSION" ]; then
-            echo "version_changed=true" >> $GITHUB_OUTPUT
-            echo "Version changed from $NPM_VERSION to $PACKAGE_VERSION"
-          else
-            echo "version_changed=false" >> $GITHUB_OUTPUT
-            echo "Version unchanged: $PACKAGE_VERSION"
-          fi
-
-      - name: Publish to NPM
-        if: steps.version-check.outputs.version_changed == 'true'
-        run: |
-          npm publish --access public
-          echo "## 📦 NPM Package Published" >> $GITHUB_STEP_SUMMARY
-          echo "" >> $GITHUB_STEP_SUMMARY
-          echo "✅ Successfully published @happychef/algorithm@$(node -p "require('./package.json').version")" >> $GITHUB_STEP_SUMMARY
-          echo "" >> $GITHUB_STEP_SUMMARY
-          echo "🔗 [View on NPM](https://www.npmjs.com/package/@happychef/algorithm)" >> $GITHUB_STEP_SUMMARY
-        env:
-          NODE_AUTH_TOKEN: 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
-
-      - name: Skip publishing (version unchanged)
-        if: steps.version-check.outputs.version_changed == 'false'
-        run: |
-          echo "## ⏭️ Publishing Skipped" >> $GITHUB_STEP_SUMMARY
-          echo "" >> $GITHUB_STEP_SUMMARY
-          echo "Version $(node -p "require('./package.json').version") is already published" >> $GITHUB_STEP_SUMMARY
-          echo "" >> $GITHUB_STEP_SUMMARY
-          echo "💡 Bump the version in package.json to trigger publishing" >> $GITHUB_STEP_SUMMARY
-
-      - name: Create Git Tag
-        if: steps.version-check.outputs.version_changed == 'true'
-        run: |
-          PACKAGE_VERSION=$(node -p "require('./package.json').version")
-          git config user.name "github-actions[bot]"
-          git config user.email "github-actions[bot]@users.noreply.github.com"
-          git tag -a "v$PACKAGE_VERSION" -m "Release v$PACKAGE_VERSION"
-          git push origin "v$PACKAGE_VERSION"
-          echo "## 🏷️ Git Tag Created" >> $GITHUB_STEP_SUMMARY
-          echo "" >> $GITHUB_STEP_SUMMARY
-          echo "Created and pushed tag: v$PACKAGE_VERSION" >> $GITHUB_STEP_SUMMARY
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+name: CI/CD Pipeline
+
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+    branches:
+      - main
+    types: [opened, synchronize, reopened]
+
+jobs:
+  publish:
+    name: Publish to NPM
+    runs-on: ubuntu-latest
+    if: github.ref == 'refs/heads/main' && github.event_name == 'push'
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: '20.x'
+          registry-url: 'https://registry.npmjs.org'
+          cache: 'npm'
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Check if version changed
+        id: version-check
+        run: |
+          PACKAGE_VERSION=$(node -p "require('./package.json').version")
+          NPM_VERSION=$(npm view @happychef/algorithm version 2>/dev/null || echo "0.0.0")
+          echo "Package version: $PACKAGE_VERSION"
+          echo "NPM version: $NPM_VERSION"
+          if [ "$PACKAGE_VERSION" != "$NPM_VERSION" ]; then
+            echo "version_changed=true" >> $GITHUB_OUTPUT
+            echo "Version changed from $NPM_VERSION to $PACKAGE_VERSION"
+          else
+            echo "version_changed=false" >> $GITHUB_OUTPUT
+            echo "Version unchanged: $PACKAGE_VERSION"
+          fi
+
+      - name: Publish to NPM
+        if: steps.version-check.outputs.version_changed == 'true'
+        run: |
+          npm publish --access public
+          echo "## 📦 NPM Package Published" >> $GITHUB_STEP_SUMMARY
+          echo "" >> $GITHUB_STEP_SUMMARY
+          echo "✅ Successfully published @happychef/algorithm@$(node -p "require('./package.json').version")" >> $GITHUB_STEP_SUMMARY
+          echo "" >> $GITHUB_STEP_SUMMARY
+          echo "🔗 [View on NPM](https://www.npmjs.com/package/@happychef/algorithm)" >> $GITHUB_STEP_SUMMARY
+        env:
+          NODE_AUTH_TOKEN: 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
+
+      - name: Skip publishing (version unchanged)
+        if: steps.version-check.outputs.version_changed == 'false'
+        run: |
+          echo "## ⏭️ Publishing Skipped" >> $GITHUB_STEP_SUMMARY
+          echo "" >> $GITHUB_STEP_SUMMARY
+          echo "Version $(node -p "require('./package.json').version") is already published" >> $GITHUB_STEP_SUMMARY
+          echo "" >> $GITHUB_STEP_SUMMARY
+          echo "💡 Bump the version in package.json to trigger publishing" >> $GITHUB_STEP_SUMMARY
+
+      - name: Create Git Tag
+        if: steps.version-check.outputs.version_changed == 'true'
+        run: |
+          PACKAGE_VERSION=$(node -p "require('./package.json').version")
+          git config user.name "github-actions[bot]"
+          git config user.email "github-actions[bot]@users.noreply.github.com"
+          git tag -a "v$PACKAGE_VERSION" -m "Release v$PACKAGE_VERSION"
+          git push origin "v$PACKAGE_VERSION"
+          echo "## 🏷️ Git Tag Created" >> $GITHUB_STEP_SUMMARY
+          echo "" >> $GITHUB_STEP_SUMMARY
+          echo "Created and pushed tag: v$PACKAGE_VERSION" >> $GITHUB_STEP_SUMMARY
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

package/BRANCH_PROTECTION_SETUP.md

@@ -1,167 +1,167 @@
-# Branch Protection Setup Guide
-
-This guide explains how to configure GitHub branch protection rules to require all tests to pass before merging pull requests.
-
-## Why Branch Protection?
-
-Branch protection ensures:
-- ✅ All tests must pass before merging PRs
-- ✅ No direct pushes to main without review (optional)
-- ✅ Code quality is maintained
-- ✅ Broken code never reaches production
-
-## Setup Instructions
-
-### Step 1: Go to Branch Protection Settings
-
-1. Navigate to your GitHub repository: `https://github.com/thibaultvandesompele2/15-happy-algorithm`
-2. Click on **Settings** (tab at the top)
-3. In the left sidebar, click **Branches** (under "Code and automation")
-4. Click **Add branch protection rule** (or **Add rule**)
-
-### Step 2: Configure the Rule
-
-#### Basic Settings:
-1. **Branch name pattern**: Enter `main`
-
-#### Required Settings:
-
-✅ **Check these boxes:**
-
-1. ☑️ **Require a pull request before merging**
-   - This prevents direct pushes to main
-   - Optional: Set "Required number of approvals" to 1 or more
-
-2. ☑️ **Require status checks to pass before merging**
-   - This is the CRITICAL setting for test enforcement
-   - Check: **Require branches to be up to date before merging**
-
-3. In the **Status checks** search box, you'll see:
-   - `Run Tests` (your test job)
-
-   ☑️ **Select both Node.js test jobs:**
-   - `Run Tests (18.x)`
-   - `Run Tests (20.x)`
-
-   *Note: These will appear after the first workflow run completes*
-
-4. ☑️ **Do not allow bypassing the above settings** (recommended)
-   - Even admins must follow these rules
-
-#### Optional but Recommended:
-
-5. ☑️ **Require conversation resolution before merging**
-   - All PR comments must be resolved
-
-6. ☑️ **Require linear history**
-   - Prevents messy merge commits
-
-### Step 3: Save
-
-1. Scroll to the bottom
-2. Click **Create** or **Save changes**
-
-## What Happens After Setup
-
-### On Pull Requests:
-- GitHub automatically runs the CI/CD tests
-- You'll see status checks at the bottom of the PR
-- **Merge button will be DISABLED** until all tests pass
-- If tests fail, you must fix them before merging
-
-### Visual Indicators:
-
-**Tests Running:**
-```
-⏳ Run Tests (18.x) — In progress
-⏳ Run Tests (20.x) — In progress
-```
-
-**Tests Passed:**
-```
-✅ Run Tests (18.x) — Passed
-✅ Run Tests (20.x) — Passed
-🟢 Merge pull request button is ENABLED
-```
-
-**Tests Failed:**
-```
-❌ Run Tests (18.x) — Failed
-❌ Run Tests (20.x) — Failed
-🔴 Merge pull request button is DISABLED
-```
-
-## Testing the Protection
-
-### Create a Test PR:
-
-1. Create a new branch:
-   ```bash
-   git checkout -b test-branch-protection
-   ```
-
-2. Make a small change:
-   ```bash
-   echo "# Test" >> test-file.txt
-   git add test-file.txt
-   git commit -m "Test branch protection"
-   git push origin test-branch-protection
-   ```
-
-3. Go to GitHub and create a pull request
-
-4. Observe:
-   - Tests run automatically
-   - Merge button is disabled until tests complete
-   - After tests pass, merge button becomes available
-
-## Workflow Behavior
-
-### For Pull Requests:
-- ✅ Runs all 70 tests on Node.js 18.x and 20.x
-- ✅ Must pass before merge is allowed
-- ✅ Shows test summary in PR
-- ❌ Does NOT publish to npm (only tests)
-
-### For Pushes to Main:
-- ✅ Runs all tests
-- ✅ If version changed AND tests pass → publishes to npm
-- ✅ Creates git tag
-- ✅ Shows summary of all actions
-
-## Troubleshooting
-
-### "Status checks not found"
-- The status checks only appear after the first workflow run completes
-- Push this branch protection setup, wait for workflow to run, then configure protection
-
-### "Can't find Run Tests in status checks"
-- Make sure the workflow has run at least once
-- Check the Actions tab to see workflow runs
-- The job name must match exactly: `Run Tests`
-
-### "Tests are running but merge button isn't disabled"
-- You need to enable "Require status checks to pass before merging"
-- Make sure you selected the specific test jobs (18.x and 20.x)
-
-## Quick Setup Checklist
-
-- [ ] Go to Settings → Branches
-- [ ] Add branch protection rule for `main`
-- [ ] Enable "Require status checks to pass before merging"
-- [ ] Select `Run Tests (18.x)` and `Run Tests (20.x)`
-- [ ] Enable "Do not allow bypassing"
-- [ ] Save the rule
-- [ ] Test with a PR
-
-## Additional Security (Optional)
-
-For additional security, you can also enable:
-
-- **Require deployments to succeed** - Wait for tests before deploying
-- **Lock branch** - Temporarily prevent all changes
-- **Restrict who can push** - Only specific users/teams can push
-
----
-
-**Result:** After setup, no code can be merged to `main` without passing all 70 tests! 🎉
+# Branch Protection Setup Guide
+
+This guide explains how to configure GitHub branch protection rules to require all tests to pass before merging pull requests.
+
+## Why Branch Protection?
+
+Branch protection ensures:
+- ✅ All tests must pass before merging PRs
+- ✅ No direct pushes to main without review (optional)
+- ✅ Code quality is maintained
+- ✅ Broken code never reaches production
+
+## Setup Instructions
+
+### Step 1: Go to Branch Protection Settings
+
+1. Navigate to your GitHub repository: `https://github.com/thibaultvandesompele2/15-happy-algorithm`
+2. Click on **Settings** (tab at the top)
+3. In the left sidebar, click **Branches** (under "Code and automation")
+4. Click **Add branch protection rule** (or **Add rule**)
+
+### Step 2: Configure the Rule
+
+#### Basic Settings:
+1. **Branch name pattern**: Enter `main`
+
+#### Required Settings:
+
+✅ **Check these boxes:**
+
+1. ☑️ **Require a pull request before merging**
+   - This prevents direct pushes to main
+   - Optional: Set "Required number of approvals" to 1 or more
+
+2. ☑️ **Require status checks to pass before merging**
+   - This is the CRITICAL setting for test enforcement
+   - Check: **Require branches to be up to date before merging**
+
+3. In the **Status checks** search box, you'll see:
+   - `Run Tests` (your test job)
+
+   ☑️ **Select both Node.js test jobs:**
+   - `Run Tests (18.x)`
+   - `Run Tests (20.x)`
+
+   *Note: These will appear after the first workflow run completes*
+
+4. ☑️ **Do not allow bypassing the above settings** (recommended)
+   - Even admins must follow these rules
+
+#### Optional but Recommended:
+
+5. ☑️ **Require conversation resolution before merging**
+   - All PR comments must be resolved
+
+6. ☑️ **Require linear history**
+   - Prevents messy merge commits
+
+### Step 3: Save
+
+1. Scroll to the bottom
+2. Click **Create** or **Save changes**
+
+## What Happens After Setup
+
+### On Pull Requests:
+- GitHub automatically runs the CI/CD tests
+- You'll see status checks at the bottom of the PR
+- **Merge button will be DISABLED** until all tests pass
+- If tests fail, you must fix them before merging
+
+### Visual Indicators:
+
+**Tests Running:**
+```
+⏳ Run Tests (18.x) — In progress
+⏳ Run Tests (20.x) — In progress
+```
+
+**Tests Passed:**
+```
+✅ Run Tests (18.x) — Passed
+✅ Run Tests (20.x) — Passed
+🟢 Merge pull request button is ENABLED
+```
+
+**Tests Failed:**
+```
+❌ Run Tests (18.x) — Failed
+❌ Run Tests (20.x) — Failed
+🔴 Merge pull request button is DISABLED
+```
+
+## Testing the Protection
+
+### Create a Test PR:
+
+1. Create a new branch:
+   ```bash
+   git checkout -b test-branch-protection
+   ```
+
+2. Make a small change:
+   ```bash
+   echo "# Test" >> test-file.txt
+   git add test-file.txt
+   git commit -m "Test branch protection"
+   git push origin test-branch-protection
+   ```
+
+3. Go to GitHub and create a pull request
+
+4. Observe:
+   - Tests run automatically
+   - Merge button is disabled until tests complete
+   - After tests pass, merge button becomes available
+
+## Workflow Behavior
+
+### For Pull Requests:
+- ✅ Runs all 70 tests on Node.js 18.x and 20.x
+- ✅ Must pass before merge is allowed
+- ✅ Shows test summary in PR
+- ❌ Does NOT publish to npm (only tests)
+
+### For Pushes to Main:
+- ✅ Runs all tests
+- ✅ If version changed AND tests pass → publishes to npm
+- ✅ Creates git tag
+- ✅ Shows summary of all actions
+
+## Troubleshooting
+
+### "Status checks not found"
+- The status checks only appear after the first workflow run completes
+- Push this branch protection setup, wait for workflow to run, then configure protection
+
+### "Can't find Run Tests in status checks"
+- Make sure the workflow has run at least once
+- Check the Actions tab to see workflow runs
+- The job name must match exactly: `Run Tests`
+
+### "Tests are running but merge button isn't disabled"
+- You need to enable "Require status checks to pass before merging"
+- Make sure you selected the specific test jobs (18.x and 20.x)
+
+## Quick Setup Checklist
+
+- [ ] Go to Settings → Branches
+- [ ] Add branch protection rule for `main`
+- [ ] Enable "Require status checks to pass before merging"
+- [ ] Select `Run Tests (18.x)` and `Run Tests (20.x)`
+- [ ] Enable "Do not allow bypassing"
+- [ ] Save the rule
+- [ ] Test with a PR
+
+## Additional Security (Optional)
+
+For additional security, you can also enable:
+
+- **Require deployments to succeed** - Wait for tests before deploying
+- **Lock branch** - Temporarily prevent all changes
+- **Restrict who can push** - Only specific users/teams can push
+
+---
+
+**Result:** After setup, no code can be merged to `main` without passing all 70 tests! 🎉

package/CHANGELOG.md

@@ -1,8 +1,8 @@
-PR 2:
-ADDED:
-- Modified the `getAvailableTimeblocks.js` file to change the default value of `uurOpVoorhand` from 4 hours to 0 hours, enabling immediate bookings when the field is not explicitly set in general settings.
-
-REMOVED:
-- No functions, features, or code were removed; only a configuration default value was updated.
-
----
+PR 2:
+ADDED:
+- Modified the `getAvailableTimeblocks.js` file to change the default value of `uurOpVoorhand` from 4 hours to 0 hours, enabling immediate bookings when the field is not explicitly set in general settings.
+
+REMOVED:
+- No functions, features, or code were removed; only a configuration default value was updated.
+
+---