-
Notifications
You must be signed in to change notification settings - Fork 312
Avail PropertyUI types and hide sensitive fields in the destination configuration #1187
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: newjitsu
Are you sure you want to change the base?
Conversation
ikraamg
commented
Mar 24, 2025
•
edited
Loading
edited
- Make the PropertyUI type available in the destination configuration by moving it over (not sure about how to best do this).
- Hide sensitive fields in the destination configuration UI.
editor?: | ||
| "ArrayTextarea" | ||
| "StringArrayEditor" | ||
| "CodeEditor" | ||
| "SnippedEditor" | ||
| "MultiSelectWithCustomOptions" | ||
| string; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have added these types for ease of reference. They look to be the only ones currently supported. I have not removed the acceptance of the string
type since there is a runtime check for the editor type and I wanted to tread lightly with this change.
@@ -28,7 +30,6 @@ import intercomIcon from "./icons/intercom"; | |||
import webhookIcon from "./icons/webhook"; | |||
import { branding } from "../branding"; | |||
import * as meta from "@jitsu/core-functions/src/meta"; | |||
import { HubspotCredentials } from "@jitsu/core-functions/src/meta"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was already available via meta.HubspotCredentials