Convert IATS Settings to be standard practice #437
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.
Iats Settings are currently done in a non standard way in a couple of different ways
This aims to address this by adding metadata for each individual setting and split up the array into individual settings rather than in the single array.
This function adds in helper function CRM_Iats_Utils::getSettings to handle the two different formats. This also has an upgrade step to perform the conversion.
The other thing this PR aims to do as per https://docs.civicrm.org/dev/en/latest/framework/setting/extension/ switches to using the Generic form for settings rather than a custom one.