L3 - Default Context:
There are a couple of improvements to the custom bucket feature, as discussed in the 16/06 status meeting and the follow up meeting on 17/06, see AT.
AT:
- default bucket size is not 1 but just ensured to be greater than 0 (only if it is equal to 0 does it default to 1)
- rounding:
- default bucket size is rounded up to the nearest power of 10
- default baseline is rounded down to the nearest power of 10
- Configuration settings:
- related custom bucket fields for number variables are moved to a separate dto
- this dto includes a bool indicator on whether or not custom buckets are being used
- allow the frontend to use String instead of double variables for bucket size and baseline
- if the user configures an invalid baseline, the backend returns an empty result
- when switching on the custom bucket settings for the first time, we set the following default values:
- bucket size: 10
- baseline: 0