-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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): fix additional properties issue #7434
Conversation
✅ Deploy Preview for dev-web-novu ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
currentPath += `.${part}`; | ||
const valueSearch = _.get(variableSchema, currentPath); | ||
if (additionalPropertiesValue !== undefined) { | ||
return { isValid: additionalPropertiesValue === true }; |
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 key change, if additionalPropertiesValue === true
we will allow arbitrary variables.
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.
mostly refactoring to more readable code.
✅ Deploy Preview for dashboard-v2-novu-staging ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
What changed? Why was the change needed?
This PR enables issue management to use schemas' additional properties flag.
Screenshots
Expand for optional sections
Related enterprise PR
Special notes for your reviewer