Carter is framework that is a thin layer of extension methods and functionality over ASP.NET Core allowing code to be more explicit and most importantly more enjoyable.
Currently the only way to customise registrations of CarterModule is to not use AddCarter, and register everything yourself, which isn't a big deal. This isn't possible though, if something can't be registered because it's internal, like CarterDiagnostics.
Given it's resolvable from the container and hence accessible by users, it's really considered part of the public API - do you think it's reasonable to keep it public?
Currently the only way to customise registrations of
CarterModule
is to not useAddCarter
, and register everything yourself, which isn't a big deal. This isn't possible though, if something can't be registered because it's internal, likeCarterDiagnostics
.Given it's resolvable from the container and hence accessible by users, it's really considered part of the public API - do you think it's reasonable to keep it public?
Cheers