related #45 (comment)
Right now resolve() rely on getConfig() (https://github.com/Eywek/typoa/blob/main/src/resolve.ts#L129) to access config, which creates an implicit dependency that's hard to track.
The ideal implementation is to propagate config down the function stack. Passing it around isn't perfect, but it's simple and explicit. If that feels too noisy, we can use something lightweight like async_context to handle this more elegantly without exposing global state or relying on hidden config lookups.
related #45 (comment)
Right now
resolve()rely ongetConfig()(https://github.com/Eywek/typoa/blob/main/src/resolve.ts#L129) to access config, which creates an implicit dependency that's hard to track.The ideal implementation is to propagate config down the function stack. Passing it around isn't perfect, but it's simple and explicit. If that feels too noisy, we can use something lightweight like
async_contextto handle this more elegantly without exposing global state or relying on hidden config lookups.