You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I've used a similar pattern on my options objects in the past by creating a unit test that uses conventions and reflection to validate all of the options classes/records have a static field for Configuration name with a non-null value. CI then fails it someone adds an options object without one. The configuration section name is used in builder extensions to have each option class identify the section with which it binds.
I like this as an option (haha) though. I'll have to give it a spin.