Skip to content

Figure out a nice way to expose the core API without requiring needle DI #6

@tom-sherman

Description

@tom-sherman

This is possible today, but it's not very easy and exposes more implementation details than I'd like in the API - it requires manually constructing all of the services and manually injecting them into the relevant dependent constructors in the correct order.

I'm imagining a central LPM class (or maybe NodeRegistry?) that can be constructed and passed all of the relevant implementations into. This gives type safety but also means that we don't need to worry about the constructor injection being part of the public API, we'll just expose the class, an input object type, and a bunch of types for the services.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions