-
Notifications
You must be signed in to change notification settings - Fork 2.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
fix(core): handle undefined properties in schemas with additionalProperties #22426
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
☁️ Nx Cloud ReportCI is running/has finished running commands for commit e921535. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 6 targets
Sent with 💌 from NxCloud. |
thanks for the fix :) |
i don't like the idea of using the nullish operator and giving it a default empty object. i think the schema.additionalProperties !== undefined could be changed to schema.additionalProperties != null |
nvm addditionalProperties is not .properties carry on XD |
This does prevent the error from appearing, but I think there is a larger issue at play here because after applying this fix the property that was triggering this error is still ignored. To reproduce:
foo/project.json
Without this fix applied, you'll see the After applying the fix, the error no longer appears, but the property that triggered the error ( |
b0d8cc8
to
29d1012
Compare
thanks @mattfysh for the catch & the repro. Super helpful! |
29d1012
to
e921535
Compare
hi @FrozenPandaz |
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
fixes #22349