ENH: Explicit configuration API properties.

[mfendeksilverstripe]

ENH: Explicit configuration API properties.

Description

• Added explicit configuration API properties for existing settings
• Minor code refactor for tests (DRY code cleanup)
• No functional changes overall

Pull request checklist

• The target branch is correct
  • See picking the right version
• All commits are relevant to the purpose of the PR (e.g. no debug statements, unrelated refactoring, or arbitrary linting)
  • Small amounts of additional linting are usually okay, but if it makes it hard to concentrate on the relevant changes, ask for the unrelated changes to be reverted, and submitted as a separate PR.
• The commit messages follow our commit message guidelines
• The PR follows our contribution guidelines
• Code changes follow our coding conventions
• This change is covered with tests (or tests aren't necessary for this change)
• Any relevant User Help/Developer documentation is updated; for impactful changes, information is added to the changelog for the intended release
• CI is green

[mfendeksilverstripe]

Hey @GuySartorelli , need some guidance with this one as this is technically just a code refactor with no functional changes. I did add new configuration API properties but these are for existing settings.

[GuySartorelli]

Yup no problem. What guidance are you after specifically?

[mfendeksilverstripe]

This is a non-functional code refactor change-set. Which base branch should be used @GuySartorelli ?

[GuySartorelli]

Refactors which don't have API breaking changes should target the next minor release (so 7 in this case)