dignite / appsettingsbyconvention Goto Github PK

Hello,

Really enjoying implementing this project so far. I was wondering, would it be a stretch to support interface inheritance?

My use case:

I've got my general application stack:

• Web.A
• Web.B
• Business.A
• Business.B
• Business.Core
• Data

I'd like to put common configuration in an interface in my Business.Core project (shared with Business.A/B), but each Web.A/Business.A and Web.B/Business.B may add their own site-specific config.

Can I just have two separate configs with duplicated properties? Yes. Would it be cooler if I could have a Business.Core.IConfiguration for the common stuff and a Business.A.IConfiguration that extends Business.Core.IConfiguration to add that site-specific config? Hell yes. With dependency injection services like Autofac, I could then register your generated proxy to provide a common configuration service throughout the entire application stack, yet only expose the required subset of configuration at each layer.

I can start looking into a PR for this, if you agree. I'm thinking this would just be a slight change to InterfaceImplementationExtensions. Thoughts?