Putting the Scheduler interface in its own class. I realized that it needs to be global.
Started refactoring to allow pluggable address verification services.
Making TDTM_Runnable global so that classes outside of the package can extend it. Moving the Action enum into it to avoid having to make the class that previously contained it also global.
Renaming address-related classes.
Centralizing the code that talks to the SmartyStreets web service in ADDR_SmartyStreets_Gateway.
Merge dev into feature/522-multiple-addr-verification-services
Small refactoring to the SmartyStreets gateway. Adding a new label.
Merge branch 'feature/522-multiple-addr-verification-services' of https://github.com/SalesforceFoundation/Cumulus into feature/522-multiple-addr-verification-services
Adding fields to read endpoint and implementing class from. Also small refactoring.
Storing the endpoints and the class for the address validation in a custom settings. Instantiating the class dynamically.
Removing unnecessary constructors and refactoring tests accordingly.
Updating the address verification settings page.
Forgot to rename the call from the test.
Using always the org-level settings for the address validation.
The batch address validation also uses the implementation defined in the custom settings now.
Fixing bug. The verification trigger was firing again after the address update (after verification) when inserting a contact with address. It wasn't happening before because address records were not being created when a contact was inserted with an address.
Merge dev into feature/522-multiple-addr-verification-services
Merge pull request #551 from SalesforceFoundation/feature/522-multiple-addr-verification-services

Feature/522 multiple addr verification services