Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 14:13:35 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[PR #5675] [CLOSED] test: add regression tests for Prisma migration edge cases #5523

New Issue
Closed
opened 2026-06-05 15:21:37 -04:00 by yindo · 0 comments
yindo commented 2026-06-05 15:21:37 -04:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/Mintplex-Labs/anything-llm/pull/5675
Author: @Arvuno
Created: 5/21/2026
Status: ❌ Closed

Base: master ← Head: contrib/anything-llm/prisma-migration-test-v2

📝 Commits (1)

  • c0c0bfa test: add regression tests for Prisma migration edge cases

📊 Changes

1 file changed (+154 additions, -0 deletions)

View changed files

➕ server/prisma/__tests__/migration.test.js (+154 -0)

📄 Description

Summary

  • Added regression tests for Prisma migration edge cases in server/prisma/__tests__/migration.test.js
  • Tests cover: migration idempotency, empty string handling in optional fields, and null vs undefined distinction in Prisma queries

Problem

No tests existed to ensure Prisma migrations are idempotent and handle edge cases like empty strings vs null, and null vs undefined correctly.

Solution

Added Jest tests covering:

  1. Idempotency: Running no-op operations multiple times produces consistent results
  2. Empty string: Empty strings in optional fields are preserved (not coerced to null)
  3. Null vs undefined: null explicitly nullifies a field; undefined leaves the field unchanged
  4. Sequential operations: Multiple sequential updates are idempotent

Tests

cd server && npm test -- --testPathPattern=migration

Risk / Compatibility

  • Risk: LOW
  • Affects: Tests only, no production code changes

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/Mintplex-Labs/anything-llm/pull/5675 **Author:** [@Arvuno](https://github.com/Arvuno) **Created:** 5/21/2026 **Status:** ❌ Closed **Base:** `master` ← **Head:** `contrib/anything-llm/prisma-migration-test-v2` --- ### 📝 Commits (1) - [`c0c0bfa`](https://github.com/Mintplex-Labs/anything-llm/commit/c0c0bfa1960373690e5e8fdfdeb0e85f64db0fec) test: add regression tests for Prisma migration edge cases ### 📊 Changes **1 file changed** (+154 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `server/prisma/__tests__/migration.test.js` (+154 -0) </details> ### 📄 Description ## Summary - Added regression tests for Prisma migration edge cases in `server/prisma/__tests__/migration.test.js` - Tests cover: migration idempotency, empty string handling in optional fields, and null vs undefined distinction in Prisma queries ## Problem No tests existed to ensure Prisma migrations are idempotent and handle edge cases like empty strings vs null, and null vs undefined correctly. ## Solution Added Jest tests covering: 1. **Idempotency**: Running no-op operations multiple times produces consistent results 2. **Empty string**: Empty strings in optional fields are preserved (not coerced to null) 3. **Null vs undefined**: `null` explicitly nullifies a field; `undefined` leaves the field unchanged 4. **Sequential operations**: Multiple sequential updates are idempotent ## Tests ```bash cd server && npm test -- --testPathPattern=migration ``` ## Risk / Compatibility - Risk: LOW - Affects: Tests only, no production code changes --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-06-05 15:21:37 -04:00
yindo closed this issue 2026-06-05 15:21:37 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#5523
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?