[CDF-28123] fix(graphql): exclude extra YAML fields from upsertGraphQlDmlVersion mutation variables#3114
Conversation
…lDmlVersion mutation variables ## Bump - [x] Patch - [ ] Minor - [ ] Skip ## Changelog ### Fixed - `cdf deploy` for GraphQL data models no longer sends extra or unknown YAML keys to the `upsertGraphQlDmlVersion` mutation, and now surfaces the real API error message instead of an opaque Pydantic "Input should be an object" crash.
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. |
☂️ Code Coverage
Overall Coverage
New FilesNo new covered files... Modified FilesNo covered modified files...
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #3114 +/- ##
=======================================
Coverage 86.01% 86.01%
=======================================
Files 475 475
Lines 44319 44319
=======================================
+ Hits 38119 38120 +1
+ Misses 6200 6199 -1 🚀 New features to boost your workflow:
|
…lDmlVersion mutation variables (#3115) Empty commit to trigger the release for #3113 and #3114 (both had malformed commit bodies). ## Bump - [x] Patch - [ ] Skip ## Changelog ### Fixed - `cdf deploy` for GraphQL data models no longer sends extra or unknown YAML keys to the `upsertGraphQlDmlVersion` mutation, and now surfaces the real API error message instead of an opaque Pydantic validation crash.
2 participants
Empty commit to re-trigger the release job for #3113.
The squash merge of #3113 produced a commit with an empty body, so the release script could not find the
## Bumpmarker and exited with code 1.Bump
Changelog
Fixed
cdf deployfor GraphQL data models no longer sends extra or unknown YAML keysto the
upsertGraphQlDmlVersionmutation, and now surfaces the real API errormessage instead of an opaque Pydantic
"Input should be an object"crash.