You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: