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
{{ message }}
This repository has been archived by the owner on Nov 30, 2022. It is now read-only.
Is your feature request related to a specific problem?
In our connection type endpoint (which returns the types of connectors we support out of the box), return a version of the connection with proper casing. We currently only return our internal identifier, not a version that has the proper casing of the service.
For example, we have "hubspot", but we also would like "HubSpot".
@chriscalhoun1974 has asked for this a few times, adding it to the current sprint:
add an additional attribute to the api/v1/connection_type API endpoint payload called name or description? This new attribute would be a more friendly connector name (i.e. HubSpot). Currently, I am using the identifier which is the enum value and in lowercase.
* Expose a human readable name in the connection type endpoints.
Add a human_readable_name to the saas connector registry and a separate human readable mapping for ConnectionTypes.
* Update changelog and connection type endpoint docs.
* mypy
* Update ConnectorTemplate test.
* Mypy
* Update tests/ops/models/test_connectionconfig.py
Co-authored-by: Paul Sanders <[email protected]>
Co-authored-by: Paul Sanders <[email protected]>
* Expose a human readable name in the connection type endpoints.
Add a human_readable_name to the saas connector registry and a separate human readable mapping for ConnectionTypes.
* Update changelog and connection type endpoint docs.
* mypy
* Update ConnectorTemplate test.
* Mypy
* Update tests/ops/models/test_connectionconfig.py
Co-authored-by: Paul Sanders <[email protected]>
Co-authored-by: Paul Sanders <[email protected]>
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is your feature request related to a specific problem?
In our connection type endpoint (which returns the types of connectors we support out of the box), return a version of the connection with proper casing. We currently only return our internal identifier, not a version that has the proper casing of the service.
For example, we have "hubspot", but we also would like "HubSpot".
GET "/connection_type"
Describe the solution you'd like
Describe alternatives you've considered, if any
A description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: