DI Validation
- Q666: Why can't I inject components in a pure context?
- Q667: Why must injected components be abstract types?
- Q668: Which constructs support component injection?
- Q669: Why can't I reassign an injected component variable?
- Q670: Why must component fields be initialized or injected?
- Q671: How does EK9 prevent circular dependencies in DI?
- Q672: Why must programs declare 'with application of' for injection?
- Q673: What happens when a component is injected but not registered?
- Q674: Why can't I register two implementations for the same abstract type?
- Q675: How does EK9 validate transitive component dependencies?
- Q691: How does EK9 validate DI component registration and dependency ordering?
- Q797: How does EK9 detect circular component injection at compile time?
- Q798: What happens with missing or duplicate component registrations?
- Q892: What is the maximum number of DI registrations in an EK9 application block?
- Q1334: Why does EK9 reject two 'register' lines for the same abstract component type?