jat-feedback 3.7.1 → 4.0.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +245 -7
- package/dist/jat-feedback.js +32 -28
- package/dist/jat-feedback.mjs +2794 -2518
- package/package.json +8 -3
- package/supabase/migrations/3.9.0_parent_id_set_null_on_delete.sql +19 -0
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "jat-feedback",
|
|
3
|
-
"version": "
|
|
3
|
+
"version": "4.0.0",
|
|
4
4
|
"description": "Embeddable feedback widget for bug reports and feature requests. Captures screenshots, console logs, and user context as a web component.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"main": "dist/jat-feedback.js",
|
|
@@ -14,6 +14,9 @@
|
|
|
14
14
|
"scripts": {
|
|
15
15
|
"dev": "vite build --watch",
|
|
16
16
|
"build": "vite build",
|
|
17
|
+
"test": "vitest run",
|
|
18
|
+
"test:watch": "vitest",
|
|
19
|
+
"test:server-tools": "tsx scripts/smoke-server-tools.ts",
|
|
17
20
|
"prepublishOnly": "npm run build"
|
|
18
21
|
},
|
|
19
22
|
"keywords": [
|
|
@@ -25,7 +28,7 @@
|
|
|
25
28
|
"screenshot",
|
|
26
29
|
"console-logs"
|
|
27
30
|
],
|
|
28
|
-
"author": "
|
|
31
|
+
"author": "Developer <j@wn.ke>",
|
|
29
32
|
"license": "MIT",
|
|
30
33
|
"repository": {
|
|
31
34
|
"type": "git",
|
|
@@ -35,8 +38,10 @@
|
|
|
35
38
|
"devDependencies": {
|
|
36
39
|
"@sveltejs/vite-plugin-svelte": "^6.2.4",
|
|
37
40
|
"svelte": "^5.49.1",
|
|
41
|
+
"tsx": "^4.21.0",
|
|
38
42
|
"typescript": "^5.3.3",
|
|
39
|
-
"vite": "^6.4.1"
|
|
43
|
+
"vite": "^6.4.1",
|
|
44
|
+
"vitest": "^4.1.5"
|
|
40
45
|
},
|
|
41
46
|
"dependencies": {
|
|
42
47
|
"@page-agent/core": "^1.5.8",
|
|
@@ -0,0 +1,19 @@
|
|
|
1
|
+
-- jat-feedback 3.9.0: project_tasks.parent_id → ON DELETE SET NULL
|
|
2
|
+
--
|
|
3
|
+
-- The original 3.0.0 migration declared parent_id with no ON DELETE clause,
|
|
4
|
+
-- which defaults to NO ACTION. That meant deleting an epic with subtasks
|
|
5
|
+
-- raised `project_tasks_parent_id_fkey` and surfaced as a 500 in the IDE's
|
|
6
|
+
-- DELETE /api/tasks/:id endpoint.
|
|
7
|
+
--
|
|
8
|
+
-- The sqlite backend (lib/tasks-sqlite.js) declares the same column as
|
|
9
|
+
-- `parent_id TEXT REFERENCES tasks(id) ON DELETE SET NULL` — children become
|
|
10
|
+
-- orphans when their parent epic is deleted. Bringing postgres into line so
|
|
11
|
+
-- both backends behave the same and no app-layer workaround is needed.
|
|
12
|
+
--
|
|
13
|
+
-- Idempotent: safe to re-run.
|
|
14
|
+
|
|
15
|
+
ALTER TABLE project_tasks DROP CONSTRAINT IF EXISTS project_tasks_parent_id_fkey;
|
|
16
|
+
|
|
17
|
+
ALTER TABLE project_tasks
|
|
18
|
+
ADD CONSTRAINT project_tasks_parent_id_fkey
|
|
19
|
+
FOREIGN KEY (parent_id) REFERENCES project_tasks(id) ON DELETE SET NULL;
|