Affects Version/s: None
Fix Version/s: None
During a discussion on the PSP API, it became clear that we need to ensure that all settings/preferences that can appear in a preferences set must be schematized. That is, we no longer want to allow random settings that we know nothing about (other than their name). This decision was made for two reasons: (1) the PSP need to have metadata on any settings it want to display (2) For security/validation reasons.
In other words, we need to update the preferences sets/solutions registry and the code base so that:
- All solutions registry entries have schemas for ALL their settings
- NP sets only contain valid settings
- We support writing settings like: "http://registry.gpii.net/applications/com.microsoft.windows.screenDPI/screen-dpi": 1.75 - which would signify that this is a setting called screen-dpi for the com.microsoft.windows.screenDPI solution
- Any non-supported preferences are filtered from the preferences sets
Things that need to be clarified:
- From the notes: "The change of meaning is that this block now refers to the space BEFORE capabilitiesTransformations have acted, rather than before" – what does this mean?
- How do we handle complex settingsnames such as "Voice Profiles.Active"?
Original notes can be found here: