there were a bug were the currency exchange settings was never saved
DB: is a too tricky pattern that we'll drop in the future.
the problem with this is that we actually miss cases where a DB: should be triggered
ultimately an action should be atomic and each changes it affect should be saved without extra magic
for performance purpose we can just === check if things have actually changed and we can do this at many levels
in the future, we will try to reorganize things to allow this better, for instance splitting latest countervalues vs historical countervalues so you only save the latest more frequently..
* New translations exchange.yml (French)
* New translations password.yml (French)
* New translations manager.yml (French)
* New translations sidebar.yml (French)
* New translations settings.yml (French)
* New translations send.yml (French)
* New translations dashboard.yml (French)
* New translations common.yml (French)
* New translations settings.yml (French)
* New translations sidebar.yml (French)
* New translations exchange.yml (French)
* New translations common.yml (French)
* New translations dashboard.yml (French)
* New translations manager.yml (French)
* New translations exchange.yml (French)
* New translations send.yml (French)
* New translations sidebar.yml (French)
* New translations send.yml (French)
* New translations send.yml (French)
* New translations settings.yml (French)
* New translations password.yml (French)
* New translations settings.yml (French)
* New translations common.yml (French)
* New translations onboarding.yml (French)
Gaëtan Renaudeau
Gaëtan Renaudeau
Meriadec Pillet
meriadec
Valentin D. Pinkman
ledger-bot
NastiaS