You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a specific problem?
With #1197, we removed the SaaSType enum from the backend, and made the type field on SaaS configs fully dynamic. The frontend still contains a static SaaSType enum that should be removed to reflect the dynamic nature of SaaS config types accordingly. According to @chriscalhoun1974 , there's some nontrivial refactoring work that needs to be done on the frontend codebase to make this possible. This issue is a general placeholder to account for that work so that we don't lose track of it - more specific issues can be created as the refactoring work is better defined.
#1230 and #1231 are backend features that are likely needed in order to make this frontend refactoring possible.
Is your feature request related to a specific problem?
With #1197, we removed the
SaaSType
enum from the backend, and made thetype
field on SaaS configs fully dynamic. The frontend still contains a staticSaaSType
enum that should be removed to reflect the dynamic nature of SaaS config types accordingly. According to @chriscalhoun1974 , there's some nontrivial refactoring work that needs to be done on the frontend codebase to make this possible. This issue is a general placeholder to account for that work so that we don't lose track of it - more specific issues can be created as the refactoring work is better defined.#1230 and #1231 are backend features that are likely needed in order to make this frontend refactoring possible.
@chriscalhoun1974 please feel free to update this as you see fit!
Describe the solution you'd like
A description of what you want to happen.
Describe alternatives you've considered, if any
A description of any alternative solutions or features you've considered.
Additional context
connection_type
endpoint to include encoded logo image data in response payload #1231.The text was updated successfully, but these errors were encountered: