Update how we load settings from database #1500
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Load our settings from the database with full validation, rather then short-cutting that using the
construct()
method.Motivation and Context
@dbernstein noted in #1495 that we had a problem in our sip2 integration where settings were not being loaded with the proper enum types from the database. This turned out to be a more pervasive problem then just for that integration, and necessitated this fix.
How Has This Been Tested?
Tested with the SIP2 code where this problem was first noted and ran unit tests.
Checklist