Streamline/Automate the Process for Adding New Configuration Settings #432
Description
Why do we need this ?
- The backend codebase includes a setting service that allows developers to add new Configuration Settings using the Settings table.
- Currently, developers must manually:
- Define the Enum type and Data Class for the new settings.
- Define defaults, add checks, validators, and adapters in various files.
- Each time a new setting is added, developers must refer to previous PRs to ensure all necessary components are implemented correctly and the APIs function as expected.
- This process is redundant and cumbersome, as the validators and adapters often only depend on the defined class schema.
- The developer experience can be improved by automating these steps to provide complete or near-complete boilerplate code for new settings.
Acceptance Criteria
- Improve setting creation dev experience.
- Lower dev time for setting creation.
- Limit required context for setting creation or make a way to provide context for the setting creation flow when needed.