fix: add default value for non-nullable field with default value that needs alias#643
fix: add default value for non-nullable field with default value that needs alias#643MortGron wants to merge 2 commits into
Conversation
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. |
|
@MortGron Looks like this is consistently failing builds? (I retrigger to check). Could you please fix that so it can go through risk review? |
@thorkildcognite The build/coverage action runs the integration tests. This I cannot fix because I do not have access to the CDF project where the integration tests are: The two other build tests seems to fail in all PRs, also the ones made by renovate bot, so that problem seems to be a general one not relating to this PR |
@thorkildcognite Anders is on parental leave, lets ask @ronpal instead |
On it! |
|
Sending it back to the team for fixes. Assign it back when things are building as expected. |
Description
Reviewer: All code inside
examples/is generated.Non-nullable fields with default value that needed an alias would not have the default value set in the generated SDK. This is now fixed.
Bump
Changelog
Fixed