Legacy modules and internal dependencies detected
Gluecode
A scenario showing how legacy code can be normalized, encapsulated and moved into a more readable structure without radical rewrites.
TargetGluecode
ModoCode refactor
enlaces3 enlaces
Outputs observables4 Outputs observables
Esta vista muestra el detalle operativo del caso de uso con datos mock, logs y outputs observables. La versión real se ejecuta a través de backends LAN o del gateway de Objlab.
Modo
La demo usa datos sintéticos y no llama directamente a la VM en LAN.
Métricas mock
- Modules analyzed: 18 - Legacy classes and services identified
- Adapters generated: 7 - Compatibility layer ready
- Refactor tasks: 14 - Priority actions in the modernization plan
Software involucrado
- Legacy adapter
- Code refactoring
- Transformation layer
Backend y orquestación
- www.objlab.it gateway
- Gluecode API
- audit log
Flujo de la demo
- Open the legacy block
- Choose the refactoring path
- Run the demo flow
- Compare before and after
Mock request
{ "project": "legacy-app", "mode": "refactor", "goal": "adapter-layer", "dry_run": true }Mock response
{ "status": "ok", "modules": 18, "adapters": 7, "diff": ["rename service", "extract API boundary"] }Outputs observables
Refactoring mapAdapterLogical diffModernization tasks
Log de ejecución
Incremental refactoring plan created
3 points require source code validation
