betty Consider removing `Configuration.on

Consider removing `Configuration.on_change()`

Open bartfeenstra opened this issue 1 month ago • 0 comments

It's difficult to keep synchronized, also with configuration objects being (re)created all over the place
It's not granular enough to support individual fields on configuration objects
It's used for the GUI only. Perhaps introduce a replacement where all GUI components support something like an update method when a project changes, that takes a new project. This would allow for runtime ancestry reloads in the future as well. This would also provide perfect isolation since existing projects are not altered.

https://github.com/bartfeenstra/betty/issues/1145, so we will no longer have to rebuild services.

Jun 01 '24 17:06 bartfeenstra