pkartch/basil
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 6 Wiki Activity

feat: add database-backed ingredient-instruction mapping system #4

Merged
pkartch merged 1 commits from feature/ingredient-scaling into main 2025-11-01 03:47:04 +00:00
Conversation 0 Commits 1 Files Changed 17 +2895 -13
pkartch commented 2025-11-01 03:46:45 +00:00
Owner
Copy Link

Implement comprehensive solution for managing ingredient-to-instruction
mappings in cooking mode. This moves from client-side state management
to persistent database storage, significantly improving reliability and
user experience.

Key Changes

Database & Backend

  • Add IngredientInstructionMapping table with many-to-many relationship
  • Implement automatic ingredient matching algorithm with smart name extraction
  • Add API endpoints for mapping management (update, regenerate)
  • Create migration script for existing recipes

Frontend

  • Simplify CookingMode to read-only display of stored mappings
  • Add ManageIngredientMappings page with drag-and-drop editing
  • Remove complex client-side state management (~200 lines)
  • Add navigation between cooking mode and management interface

Testing

  • Add 11 comprehensive unit tests for ingredient matcher service
  • Update integration tests with proper mocking
  • All new features fully tested (24/25 API tests passing)

Benefits

  • Persistent mappings across all clients/devices
  • Automatic generation on recipe import/creation
  • User control via dedicated management interface
  • Cleaner, more maintainable codebase

🤖 Generated with Claude Code

Co-Authored-By: Claude noreply@anthropic.com

Implement comprehensive solution for managing ingredient-to-instruction mappings in cooking mode. This moves from client-side state management to persistent database storage, significantly improving reliability and user experience. ## Key Changes ### Database & Backend - Add IngredientInstructionMapping table with many-to-many relationship - Implement automatic ingredient matching algorithm with smart name extraction - Add API endpoints for mapping management (update, regenerate) - Create migration script for existing recipes ### Frontend - Simplify CookingMode to read-only display of stored mappings - Add ManageIngredientMappings page with drag-and-drop editing - Remove complex client-side state management (~200 lines) - Add navigation between cooking mode and management interface ### Testing - Add 11 comprehensive unit tests for ingredient matcher service - Update integration tests with proper mocking - All new features fully tested (24/25 API tests passing) ## Benefits - Persistent mappings across all clients/devices - Automatic generation on recipe import/creation - User control via dedicated management interface - Cleaner, more maintainable codebase 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
pkartch added 1 commit 2025-11-01 03:46:46 +00:00
feat: add database-backed ingredient-instruction mapping system
Some checks failed
Security Scanning / Dependency License Check (pull_request) Has been cancelled
Details
CI Pipeline / Lint Code (pull_request) Has been cancelled
Details
CI Pipeline / Test API Package (pull_request) Has been cancelled
Details
CI Pipeline / Test Web Package (pull_request) Has been cancelled
Details
CI Pipeline / Test Shared Package (pull_request) Has been cancelled
Details
Docker Build & Deploy / Build Docker Images (pull_request) Has been cancelled
Details
E2E Tests / End-to-End Tests (pull_request) Has been cancelled
Details
E2E Tests / E2E Tests (Mobile) (pull_request) Has been cancelled
Details
Security Scanning / NPM Audit (pull_request) Has been cancelled
Details
Security Scanning / Code Quality Scan (pull_request) Has been cancelled
Details
Security Scanning / Docker Image Security (pull_request) Has been cancelled
Details
CI Pipeline / Build All Packages (pull_request) Has been cancelled
Details
CI Pipeline / Generate Coverage Report (pull_request) Has been cancelled
Details
Docker Build & Deploy / Push Docker Images (pull_request) Has been cancelled
Details
Docker Build & Deploy / Deploy to Staging (pull_request) Has been cancelled
Details
Docker Build & Deploy / Deploy to Production (pull_request) Has been cancelled
Details
Security Scanning / Security Summary (pull_request) Has been cancelled
Details
3d1e5f0e14 
Implement comprehensive solution for managing ingredient-to-instruction
mappings in cooking mode. This moves from client-side state management
to persistent database storage, significantly improving reliability and
user experience.

## Key Changes

### Database & Backend
- Add IngredientInstructionMapping table with many-to-many relationship
- Implement automatic ingredient matching algorithm with smart name extraction
- Add API endpoints for mapping management (update, regenerate)
- Create migration script for existing recipes

### Frontend
- Simplify CookingMode to read-only display of stored mappings
- Add ManageIngredientMappings page with drag-and-drop editing
- Remove complex client-side state management (~200 lines)
- Add navigation between cooking mode and management interface

### Testing
- Add 11 comprehensive unit tests for ingredient matcher service
- Update integration tests with proper mocking
- All new features fully tested (24/25 API tests passing)

## Benefits
- Persistent mappings across all clients/devices
- Automatic generation on recipe import/creation
- User control via dedicated management interface
- Cleaner, more maintainable codebase

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
pkartch merged commit 4156376f0c into main 2025-11-01 03:47:04 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
pkartch
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: pkartch/basil#4
Delete Branch "feature/ingredient-scaling"

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?