Skip to content

feat(frontend): implement engine connection routing integration for Issue #127 - #161

Merged
BerryUIKI merged 4 commits into
devfrom
feature/frontend-engine-connection-routing
Oct 6, 2026
Merged

BerryUIKI merged 4 commits into
devfrom
feature/frontend-engine-connection-routing

Conversation

@BerryUIKI

Copy link
Copy Markdown
Owner

Summary

Implements comprehensive frontend integration for engine connection routing to support stable connection identifiers and proper request routing.

Changes

  • TypeScript Types: Added connection_id field to CreativeActionRequest and GenerationProvenance with legacy engine_id fallback
  • Creative Store: Implemented connection ID mapping with automatic conversion from legacy engine IDs
    • managed_comfyui → comfyui-managed
    • managed_webui → webui-managed
  • Engine Store: Added connection_id tracking and ownership-based lifecycle control enforcement
  • Lifecycle Controls: Route start/stop operations by engine type and prevent external engine control
  • UI Updates: Updated CreationDock to use stable connection IDs in engine selection
  • Test Coverage: Added 13 comprehensive tests for mapping, routing, and compatibility

Test Results

  • ✅ Backend: 9/9 connection routing tests passed
  • ✅ Frontend: 13/13 connection routing tests passed
  • ✅ All existing tests continue to pass (260 backend, 41 frontend)

Backward Compatibility

  • Both connection_id and engine_id included in requests
  • Legacy engine IDs automatically mapped to stable connection IDs
  • Existing code continues to work without modification

Closes #127

…ssue #127

- Add connection_id field to CreativeActionRequest and GenerationProvenance types
- Update creative store to support stable connection IDs with legacy engine_id fallback
- Implement connection ID mapping in setEngineId (managed_comfyui -> comfyui-managed)
- Update engine store to include connection_id in instances and enforce ownership
- Modify lifecycle controls to route by engine type and prevent external engine control
- Update CreationDock UI to use connection_id in engine selection dropdown
- Add comprehensive test suite with 13 tests covering mapping, routing, and compatibility
- Maintain backward compatibility by including both connection_id and engine_id in requests

Tests:
- Backend: 9/9 connection routing tests passed
- Frontend: 13/13 connection routing tests passed

Related: #127
@BerryUIKI
BerryUIKI enabled auto-merge (squash) October 6, 2026 21:18
- Remove unused engineId and setEngineId from CreationDock destructuring
- Add missing connection_id to test provenance object in creativeStore.test.ts
- Replace global.fetch with globalThis.fetch for TypeScript compatibility in tests
@BerryUIKI
BerryUIKI merged commit 50b0ece into dev Oct 6, 2026
3 checks passed
@BerryUIKI
BerryUIKI deleted the feature/frontend-engine-connection-routing branch October 6, 2026 21:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant