Show Wiring (Spring4D DI + DFM events)
Surfaces bindings the compiler does not make obvious: Spring4D container registrations and DFM event hookups for a type.
Read this when you are tracing how an interface gets resolved or which handler a DFM event really calls: it shows the Spring4D container registrations and DFM event hookups the compiler does not make obvious.
How to run it
Full flag list: wiring in the CLI reference.
Flags
| Flag | Argument | Meaning | Default |
|---|---|---|---|
--qname | <IIntf|TForm> | ||
--db | <file.sqlite> | ||
--format |
Where to click
- RAD Studio main menu: drag-lint > Uses & Dependencies > Show Wiring (Spring4D DI + DFM events)...
Details
Surfaces bindings the compiler does not make obvious: Spring4D container registrations and DFM event hookups for a type. Reach for it when tracing how an interface gets resolved, or which handler a DFM event actually calls.
Running it from the CLI
drag-lint wiring --qname <IIntf|TForm> [--db <file.sqlite>] [--format text|json]A separate coverage mode is also documented:
drag-lint wiring --coverage [--db <file.sqlite>] [--format text|json]which reports DI registrations not yet resolved to an interface-to-type pairing.
Reaching it in the IDE
drag-lint > Uses & Dependencies > Show Wiring (Spring4D DI + DFM events)...
What it needs
Optional. An index is not marked required, but the wiring data comes from whatever has been indexed.
Example
Illustrative only:
drag-lint wiring --qname MyApp.TfrmMain --db C:\Projects\MyApp\_D-RAG\MyApp.sqlite --format textThis would list Spring4D DI registrations and DFM event edges touching TfrmMain.