fix: extract appointmentDate for multi_claim/batch_claim/preauth intents
The classifier prompt only told the AI that appointmentDate applies to schedule_appointment/claim_only/check_and_claim, so a trailing date like "all on 6/23/26" was dropped for multi-patient claims even though the workflow already reads c.appointmentDate for those intents and silently defaulted to today. Also add Prisma config/seed scripts and shopping-vendor types/schema updates. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
18
packages/db/prisma/prisma.config.js
Normal file
18
packages/db/prisma/prisma.config.js
Normal file
@@ -0,0 +1,18 @@
|
||||
"use strict";
|
||||
var __importDefault = (this && this.__importDefault) || function (mod) {
|
||||
return (mod && mod.__esModule) ? mod : { "default": mod };
|
||||
};
|
||||
Object.defineProperty(exports, "__esModule", { value: true });
|
||||
const dotenv_1 = __importDefault(require("dotenv"));
|
||||
const path_1 = __importDefault(require("path"));
|
||||
const config_1 = require("prisma/config");
|
||||
dotenv_1.default.config({ path: path_1.default.resolve(__dirname, ".env") });
|
||||
exports.default = (0, config_1.defineConfig)({
|
||||
schema: "schema.prisma",
|
||||
datasource: {
|
||||
url: (0, config_1.env)("DATABASE_URL"),
|
||||
},
|
||||
migrations: {
|
||||
seed: "ts-node prisma/seed.ts",
|
||||
},
|
||||
});
|
||||
Reference in New Issue
Block a user