@elyracode/laravel 0.7.12 → 0.7.14

package/extensions/index.ts

@@ -414,7 +414,7 @@ export default function (elyra: ExtensionAPI): void {
 		cwd = ctx.cwd;
 
 		// Only register tools when running inside a Laravel project
-		if (!toolsRegistered && isLaravelProject(getCwd())) {
+		if (!toolsRegistered && isLaravelProject(cwd)) {
 			toolsRegistered = true;
 			registerTools(elyra, () => cwd);
 		}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@elyracode/laravel",
-  "version": "0.7.12",
+  "version": "0.7.14",
   "description": "Deep Laravel project understanding for Elyra -- model relationships, route mapping, architecture analysis",
   "type": "module",
   "keywords": [

package/skills/elyra-laravel/SKILL.md

@@ -21,6 +21,20 @@ Use Laravel tools when:
 | `laravel_routes` | Understanding existing routes, middleware, and controllers before adding new endpoints |
 | `laravel_analyze` | Understanding project conventions and patterns before writing any code |
 
+## Combining with Database Tools
+
+If `@elyracode/db-tools` is installed, use BOTH for full understanding:
+
+1. `laravel_models` — shows PHP-side: relationships, fillable, casts, scopes, traits
+2. `db_schema` or database tools — shows DB-side: actual columns, types, indexes, foreign keys
+
+Compare the two to find gaps:
+- Columns in DB but not in `$fillable` (may need adding)
+- Columns in `$fillable` but not in DB (missing migration)
+- Columns without `$casts` that should have them (dates, enums, JSON)
+- Missing indexes on foreign key columns
+- Missing foreign key constraints on `_id` columns
+
 ## Key Principle
 
 Run `laravel_analyze` or `laravel_models` BEFORE generating Laravel code. Match the project's existing patterns — if it uses Actions, don't create Services. If controllers are invokable, don't create resource controllers.