cratis-fundamentals-type-discovery

Topics in the source

• Cratis implementation discovery
• Verified product sources
• Route near misses
• When you need this
• Step 1 — Confirm the implementations are discoverable
• Step 2 — Choose the lifetime with an attribute
• Step 3 — Inject IInstancesOf in the consumer
• Step 4 — Delete the dead registrations

services.AddSingleton () looks free at the registration line. The cost arrives later: a new implementation in another folder does nothing until someone remembers the line, a removed one leaves a registration that fails at startup, and every specification setup has to mirror the composition root. IInstancesOf moves that knowledge into the implementation. Adding or removing one becomes a single-file change. | Package | Purpose | | --- | --- | | Cratis.Fundamentals | IInstancesOf , IImplementationsOf , ITypes, convention bindings and the bundled Cratis.Fundamentals.TypeDiscovery.Generator | Reverify against the Cratis Fundamentals repository before claiming support for another version. The consumer needs one implementation chosen at composition time: constructor-inject the interface and let the IFoo → Foo convention resolve it. This skill does not apply. The method returns a sequence of values to a caller: IEnumerable (or IReadOnlyList ) is still the right return type. The rule is about injecting implementations of an abstraction, not about returning values. You only need the types, never instances: inject IImplementationsOf , which enumerates Type rather than T. The consumer of an ab

This is an excerpt. Refer to the complete source and its current requirements.