-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Description
A scenario I come across often is changing a setting and some other part of the system not realising a value has changed.
Example:
module-invoice's settings class loads the payment driver service in order to detect which rivers are available. This internally does a check to see which is enabled, calling appSettings. This would happen as part of database migrations.
Later on, in the app migrations, we set a different driver. When running tests and we attempt to make a charge, the original value is used, and the new value is deemed invalid.
What would be nice is if setting objects could be refreshed, triggering a cascade of value updates meaning that wherever a value is used the next time it is checked, the updated value is found.
Metadata
Metadata
Assignees
Labels
No labels