feature request #8062
closedMake default preferences deletable serverside
100%
Description
Currently when storing a CdmPreference it can not be checked if it holds the default value and therefore can be deleted. This is because CdmPreference holds the predicate as string only and therefore does not hold the default value. Only for those predicates defined server side it is possible to retrieve default value.
There are various possibilities to pass the default value.
- Use IPreferencePredicate in CdmPreference.prefKey instead of String
- Override set(CdmPreference) in PreferenceService to allow to pass an extra attribute "default value"
- Leave it to the client to delete default values (this requires a delete method) => we finally took this solution, see also #8045
- tbc
Related issues
Updated by Andreas Müller over 5 years ago
- Related to bug #7849: Improve DB Preferences handling and saving in TaxEditor added
Updated by Andreas Müller over 5 years ago
- Related to feature request #7902: Allow default values for PreferencePredicates added
Updated by Andreas Müller over 5 years ago
The first implementation seems to work for all server side preferences using PreferencePredicates. This is only a first step.
Updated by Andreas Müller over 5 years ago
- Status changed from New to In Progress
- Target version changed from Release 5.5 to Release 5.6
Updated by Andreas Müller over 5 years ago
- Target version changed from Release 5.6 to Release 5.7
Updated by Andreas Müller about 5 years ago
- Target version changed from Release 5.7 to Release 5.8
Updated by Andreas Müller about 3 years ago
- Status changed from In Progress to Resolved
- Target version changed from Release 5.8 to Release 5.25
- % Done changed from 0 to 30
Check, how far this is fixed. Create open issues ticket and move this ticket back to 5.8
Updated by Andreas Müller about 3 years ago
- Target version changed from Release 5.25 to Release 5.51
Updated by Andreas Müller almost 3 years ago
- Priority changed from Highest to Priority14
Updated by Andreas Müller almost 3 years ago
- Related to feature request #8045: Improve handling of default values and override in local preferences added
Updated by Andreas Müller almost 3 years ago
- Description updated (diff)
In later discussions (e.g. related to #8045) we decided that it makes sense to distinguish default values (not existing values) from preferences that has the same value as the default value. This has an advantage in case a default value of a preference changes as you can still distinguish between an explicitly chosen value (similar to the default value) and a non-chosen value (a real default value).
Also it makes the handling between serverside preferences and client side preferences easier.
Updated by Andreas Müller almost 3 years ago
- Copied to task #9826: Move pure TaxEditor predicates back to taxeditor code added
Updated by Andreas Müller almost 3 years ago
- Description updated (diff)
- Status changed from Resolved to Closed
- Target version changed from Release 5.51 to Release 5.8
- % Done changed from 30 to 100