@eeplatform/basic-edu 1.10.39 → 1.10.40

package/.github/workflows/publish.yml

@@ -17,23 +17,22 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
 
       - uses: actions/setup-node@v4
         with:
           node-version: 20.x
-          cache: "yarn" # Use yarn for caching
-          cache-dependency-path: yarn.lock # Cache Yarn lockfile
-
-      - run: yarn install --immutable # Install dependencies with immutable lockfile
+          cache: "yarn"
+          cache-dependency-path: yarn.lock
 
-      - name: Create .npmrc for publishing
-        run: |
-          echo '//registry.npmjs.org/:_authToken=${{ secrets.NPM_TOKEN }}' > ~/.npmrc
+      - run: yarn install --immutable
 
       - name: Create Release Pull Request or Publish
         id: changesets
         uses: changesets/action@v1
         with:
-          publish: yarn release # Use yarn for publishing
+          publish: yarn release
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # @eeplatform/basic-edu
 
+## 1.10.40
+
+### Patch Changes
+
+- ef02db4: Update dependencies
+
 ## 1.10.39
 
 ### Patch Changes

package/CLAUDE.md

@@ -63,7 +63,7 @@ Multi-word resource names use dot notation in file names: `finance.journal.confi
 
 ## Error Handling
 
-Always use the typed error classes from `@goweekdays/utils` — never throw a generic `new Error()`.
+Always use the typed error classes from `@eeplatform/nodejs-utils` — never throw a generic `new Error()`.
 
 - `BadRequestError` — invalid input or a violated business rule
 - `NotFoundError` — resource does not exist
@@ -104,171 +104,3 @@ Transactions belong in the service layer only — never in a controller or repos
 - **No generic `Error` throws** — use the typed error classes above
 - **No Zod** — validation is done with Joi throughout this module
 - **No extra fields into the DB** — always validate the full request body before using any of it
-
-# Monthly Account Balance Tracking — Instruction Set
-
-## Objective
-
-Maintain a monthly balance tracker for each account using the structure:
-
-(accountId, fiscalYear, month)
-
-Each record must contain:
-
-- openingDebit
-- openingCredit
-- movementDebit
-- movementCredit
-- closingDebit
-- closingCredit
-- netBalance
-
----
-
-# 1. When Posting a Journal Entry
-
-For each journal line in a transaction:
-
-1. Identify:
-
-   - accountId
-   - transactionDate
-   - month
-   - fiscalYear
-   - debitAmount
-   - creditAmount
-
-2. Locate the balance record:
-
-(accountId, fiscalYear, month)
-
----
-
-# 2. If Balance Record Exists
-
-Update the movement values.
-
-If the journal line is debit:
-
-movementDebit += debitAmount
-
-If the journal line is credit:
-
-movementCredit += creditAmount
-
-Then recompute the closing balance.
-
----
-
-# 3. If Balance Record Does NOT Exist
-
-Create a new balance record.
-
-Determine the opening balance using the following rules.
-
-## Rule A — Previous Month Record Exists
-
-Find the latest previous balance record for the same account.
-
-(accountId, previousMonth, fiscalYear)
-
-Set the opening balance:
-
-openingDebit = previousRecord.closingDebit
-openingCredit = previousRecord.closingCredit
-
-## Rule B — No Previous Record Exists
-
-This means the account is used for the first time.
-
-Set:
-
-openingDebit = 0
-openingCredit = 0
-
-## Initialize Movement
-
-After determining the opening balance:
-
-movementDebit = debitAmount
-movementCredit = creditAmount
-
----
-
-# 4. Recompute Closing Balance
-
-After movement updates, compute the net balance.
-
-netBalance = (openingDebit + movementDebit) - (openingCredit + movementCredit)
-
-If netBalance > 0:
-
-closingDebit = netBalance
-closingCredit = 0
-
-If netBalance < 0:
-
-closingDebit = 0
-closingCredit = abs(netBalance)
-
-If netBalance == 0:
-
-closingDebit = 0
-closingCredit = 0
-
-The `netBalance` field should always store the computed value so the system can quickly determine whether the account has a debit or credit balance without recalculating.
-
----
-
-# 5. Month-to-Month Carry Forward Rule
-
-When a new month record is created:
-
-opening balance = previous month closing balance
-
-Example:
-
-January closing = 8,000 debit
-February opening = 8,000 debit
-
----
-
-# 6. Summary of Posting Flow
-
-For each journal line:
-
-1. Determine account, fiscalYear, and month
-2. Find balance record
-3. If record exists → update movement
-4. If record does not exist
-
-   - find previous balance record
-   - set opening = previous closing (or zero)
-   - create new balance record
-
-5. Update movement values
-6. Recompute closing balance
-
----
-
-# 7. Important Principle
-
-Opening balance always represents:
-
-balance before the period starts
-
-Therefore:
-
-opening = previous closing
-
-If no previous record exists:
-
-opening = 0
-
----
-
-This logic ensures:
-
-- continuous balance tracking
-- correct month-to-month carry over
-- efficient financial reporting without recalculating all journal entries

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@eeplatform/basic-edu",
   "license": "MIT",
-  "version": "1.10.39",
+  "version": "1.10.40",
   "main": "dist/index.js",
   "module": "dist/index.mjs",
   "types": "dist/index.d.ts",
@@ -20,7 +20,7 @@
   },
   "dependencies": {
     "@eeplatform/core": "^1.8.7",
-    "@eeplatform/nodejs-utils": "^1.2.2",
+    "@eeplatform/nodejs-utils": "^1.2.5",
     "dotenv": "^16.4.5",
     "express": "^4.21.2",
     "handlebars": "^4.7.8",