Refactor #30860
Tracker #29939: Improve setting definition DSL and move setting registry to memory
Create SettingPresenter as a proxy for setting UI values
Related issues
Associated revisions
History
#1
Updated by The Foreman Bot over 2 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/8001 added
#2
Updated by Ondřej Ezr over 2 years ago
- Related to Refactor #30861: Move setting value collections to SettingPresenter added
#3
Updated by Ondřej Ezr over 2 years ago
- Related to deleted (Refactor #30861: Move setting value collections to SettingPresenter)
#4
Updated by Ondřej Ezr over 2 years ago
- Precedes Refactor #30861: Move setting value collections to SettingPresenter added
#5
Updated by Ondřej Ezr over 2 years ago
- Precedes deleted (Refactor #30861: Move setting value collections to SettingPresenter)
#6
Updated by Ondřej Ezr over 2 years ago
- Blocks Refactor #30861: Move setting value collections to SettingPresenter added
#7
Updated by Ondřej Ezr over 2 years ago
- Blocks Feature #30862: Introduce SettingRegistry as a setting inventory added
#8
Updated by The Foreman Bot over 2 years ago
- Fixed in Releases 2.3.0 added
#9
Updated by Ondřej Ezr over 2 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset foreman|e037f70d6fe7c0f282db22fcdc6221c49dc35b15.
Fixes #30860 - introduce SettingPresenter (#8001)
Introduces SettingPresenter, that should keep all the information about setting.
This aims to keep such information only in the code and remove them from the DB.
This only prepares the ground for future drop of this information from DB.
We should slowly move most of the logic to the SettingPresenter from Setting.
Setting model should be kept only as an interface to the key/value storage.
DB will only hold key/value of changed settings.