-
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(dashboard): Add a disableOutputSanitization option for in app steps #7456
feat(dashboard): Add a disableOutputSanitization option for in app steps #7456
Conversation
✅ Deploy Preview for dev-web-novu ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for dashboard-v2-novu-staging ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
@@ -215,6 +213,8 @@ export class ConstructFrameworkWorkflow { | |||
// TODO: fix the `JSONSchemaDto` type to enforce a non-primitive schema type. | |||
controlSchema: staticStep.template!.controls!.schema as JsonSchema, | |||
skip: (controlValues: Record<string, unknown>) => this.processSkipOption(controlValues, fullPayloadForRender), | |||
disableOutputSanitization: | |||
(staticStep.controlVariables?.disableOutputSanitization as boolean | undefined) ?? 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.
do we need to transfer this flat to boolean just in case we stored it in the db as "false"
in addition as mentioned in the DM staticStep.controlVariables is not available from the database. we need either fetch those controls or pass them from the framework to this scope.
37d296e
to
1e906ec
Compare
@novu/client
@novu/headless
@novu/node
@novu/notification-center
novu
@novu/providers
@novu/shared
commit: |
1e906ec
to
f759279
Compare
f759279
to
8b4c88e
Compare
8b4c88e
to
e98e667
Compare
e98e667
to
16b350b
Compare
16b350b
to
a251050
Compare
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.
Looks good to me, great job! :)
Please ensure that we remove disableOutputSanitization
in InAppOutputRendererUsecase
, just like we remove skip
. Unfortunately, we don’t have strict types there yet. I believe the framework (via the Output Schema) could throw a validation error for this mismatch.
On a related note, have we tested the full flow, including trigger execution?
a251050
to
1b682f7
Compare
What changed? Why was the change needed?
Screenshots
Expand for optional sections
Related enterprise PR
Special notes for your reviewer