Skip to content

Conversation

udvasude
Copy link

This PR addresses issues with risk seeding that resulted in the removal of required fields and corruption of otherwise valid model.yaml files. The root cause was identified as improper use of the omitempty tag during marshalling/unmarshalling.

Details:

  • Removed omitempty from struct fields that are marked as required in the schema, ensuring these fields are always present in the output.
  • Some fields are marked as nullable but are still required by the schema; these must not use omitempty to avoid accidental omission.

@udvasude udvasude changed the title Fix broken risk tracking cause by omitempty used on required fields Fix: Remove omitempty from required fields to prevent model corruption during risk seeding Oct 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant