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
ModeCode refactor
links3 links
Observable outputs4 Observable outputs
This view shows the operational detail of the use case with mock data, logs and observable outputs. The real version runs through LAN backends or the Objlab gateway.
Mode
The demo uses synthetic data and does not call the LAN VM directly.
Mock metrics
- Modules analyzed: 18 - Legacy classes and services identified
- Adapters generated: 7 - Compatibility layer ready
- Refactor tasks: 14 - Priority actions in the modernization plan
Software involved
- Legacy adapter
- Code refactoring
- Transformation layer
Backend and orchestration
- www.objlab.it gateway
- Gluecode API
- audit log
Demo flow
- 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"] }Observable outputs
Refactoring mapAdapterLogical diffModernization tasks
Execution log
Incremental refactoring plan created
3 points require source code validation
