-
Notifications
You must be signed in to change notification settings - Fork 4k
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
feat(api-service): decode special characters #7881
base: next
Are you sure you want to change the base?
feat(api-service): decode special characters #7881
Conversation
✅ Deploy Preview for dashboard-v2-novu-staging ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
commit: |
@@ -829,6 +829,19 @@ export class Client { | |||
return getCodeResult; | |||
} | |||
} | |||
|
|||
type ChannelStepOption = { |
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.
the option type here is not correct and is hard to reuse because of its dynamic nature; therefore, i created a simple type for now.
in addition I created a ticket to solve the typing issue.
const skipOutputSanitization = (stepType: string, outputKey: string) => { | ||
// Skip sanitization for string values that aren't HTML | ||
if (outputKey === 'subject' && stepType === 'email') { | ||
return true; | ||
} | ||
|
||
return false; | ||
}; |
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.
We need to change this and do the opposite and sanitize only HTML outputs instead, as this could happen on all of the channels.
…-properly-for-email-subject
What changed? Why was the change needed?
Screenshots
Expand for optional sections
Related enterprise PR
Special notes for your reviewer