Merge configs to Connection Providers #1085
Description
Summary
Currently there's more than one config per provider, we can unify those configs under connection provider which references all configs and is also a scriptable object.
Suggested features or ways to address the summary
Move config fields and variables into the respective connection providers.
Motivation
A lighter more readable and simpler SDK
Acceptance Criteria
There should be one Scriptable Object per provider, in case of larger (context specific) configs we can make then serializable classes/structs serialized in connection providers.
Blockers
(OPTIONAL) [Do you see any blocker that needs to be done before implementing this feature?]
Dependencies
(OPTIONAL) [Do you know about dependencies that directly affect this issue?]
Additional Context
(OPTIONAL) [Add any other context, files, images (screenshots/videos), diagrams, or documents about the feature request here.]
Final Steps
- Give it one of these labels
Type: FeatureType: Enhancement - Add your estimation
Estimations
| Story Point | Amount of effort | Amount of time | Task Complexity | Task Risk or Uncerntainty |
|---|---|---|---|---|
| 3 | Mild efort | A day | Low complexity | Low |