Skip to content

Update all settings members to properties and update the attributes to match new UI requirements #106

@michaelbeale-IL

Description

@michaelbeale-IL

Problem:
Currently all of the settings classes just use member variables to store settings. Because of some forthcoming UI changes, we need them all changed to be properties with specific attributes associated with each data type and setting.

Task Steps:

  1. Go through all projects in the repo and identify ones that have publicly exposed settings in their implementations of the PreferencesBase class.
  2. Update the member variable to a property by adding { get: set: } where appropriate. (make sure to be mindful of any existing getter or setter logic that is present and preserve the functionality.)
  3. Replace the existing data type specific attributes (BoolDescriptor, IntDescriptor, etc.) with the following:
  • [Descriptor()] - the full description field from the old attribute.
  • [Range()] - on Elements that have a range defined in their old attributes.
  • [UIHint()] - Based on the property type. Option will include ["Slider", "ToggleSwitch", "TextBox"] and will match the intention of the preference. (use your judgement based on the description text.

Metadata

Metadata

Assignees

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions