Skip to content

Fix #124: emit SecurityStatus required spec fields - #129

Merged
pedrosakuma merged 1 commit into
mainfrom
fix/issue-124-securitystatus-fields
Aug 25, 2026
Merged

pedrosakuma merged 1 commit into
mainfrom
fix/issue-124-securitystatus-fields

Conversation

@pedrosakuma

Copy link
Copy Markdown
Owner

Summary

  • emit all populated SecurityStatus fields supported by the current DTO and FIX44 UMDF Conflated spec, including SecurityTradingStatus (326)
  • preserve optional-field behavior by only writing optional tags when values are present
  • update SecurityStatus builder tests to validate the newly emitted tags

Testing

  • dotnet test tests/B3.Umdf.FixConflated.Tests/B3.Umdf.FixConflated.Tests.csproj --filter SecurityStatusMessageBuilderTests

Fixes #124

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@pedrosakuma
pedrosakuma force-pushed the fix/issue-124-securitystatus-fields branch from 6266937 to fb40f31 Compare August 25, 2026 14:07
@pedrosakuma
pedrosakuma merged commit bdde844 into main Aug 25, 2026
7 checks passed
@pedrosakuma
pedrosakuma deleted the fix/issue-124-securitystatus-fields branch August 25, 2026 14:20
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.

SecurityStatus builder omite campos obrigatórios/spec (326 SecurityTradingStatus e outros)

1 participant