Metadata
- Source
- FLUID-6420
- Type
- Improvement
- Priority
- Major
- Status
- Closed
- Resolution
- Fixed
- Assignee
- N/A
- Reporter
- Justin Obara
- Created
2019-10-31T11:22:19.179-0400 - Updated
2024-07-22T10:35:22.802-0400 - Versions
- N/A
- Fixed Versions
-
- 4.0
- Component
-
- Prefs Framework
- UI Options
Description
Currently the start schema contains a single schema for the base set of preferences. It seems that this isn't always desirable, as it makes it hard to remove preferences. A better solution would be to split the auxiliary schema into individual grade wrapped schemas for each preference. These can then be composed into the set of preferences desired. This would be similar to how the newer preferences are have separate grades that can be merged in.
Comments
-
Justin Obara commented
2019-10-31T13:34:17.685-0400 In looking into this further, there is a question of how to best make use of the split out auxiliary schema grades. The biggest hurdle is with UIO which makes use of a pre-assembled grade. (See: https://github.com/fluid-project/infusion/blob/master/src/components/uiOptions/js/UIOptions.js#L19-L21 ). This means that it is already too late to change the preferences by an integrator with a schema.
This has me thinking though that we might be able to have an invoker as a grade. It would call fluid.prefs.builder and return the assembled grade as a grade name to UIO. Actually this could replace fluid.prefs.create.
We should also explore the possibility of just replacing fluid.prefs.builder, fluid.prefs.create, and fluid.uiOptions.prefsEditor all with a single component that took care of all of these things. In this case all prefs editors would be created with the same component, but with different configuration for the auxiliary schemas used.