Skip to content

Fix: Resolve CS8618 nullable warnings in SOAP response classes#13

Merged
petre-c merged 2 commits intomainfrom
fix/nullable-warnings
Aug 4, 2025
Merged

Fix: Resolve CS8618 nullable warnings in SOAP response classes#13
petre-c merged 2 commits intomainfrom
fix/nullable-warnings

Conversation

@petre-c
Copy link
Contributor

@petre-c petre-c commented Aug 4, 2025

Summary

  • Fixed all CS8618 nullable warnings in the SOAP response classes
  • Changed from mutable set to immutable init properties
  • Added proper nullable and required modifiers

Changes

  • Changed properties from set to init for immutability
  • Added required modifier for properties that are always present in SOAP responses
  • Made optional properties nullable with ? modifier
  • Fixed warnings in:
    • ChangePasswordResponseIo.cs
    • GetPostboxMessagesResponseIo.cs

Test Plan

  • Build completes without CS8618 warnings
  • All existing tests pass

Collaboration by Claude

Petre Chitashvili added 2 commits August 4, 2025 23:17
- Changed properties from 'set' to 'init' for immutability
- Added 'required' modifier for properties that are always present in responses
- Made optional properties nullable with '?' modifier
- Fixed warnings in ChangePasswordResponseIo and GetPostboxMessagesResponseIo

*Collaboration by Claude*
- Made core movement properties required (movementId, debitCredit, description, amount)
- Made optional properties nullable (partner info, taxpayer info, additional details)
- Ensures proper handling of SOAP responses with missing optional fields

*Collaboration by Claude*
@petre-c petre-c merged commit 31e3a58 into main Aug 4, 2025
1 check passed
@petre-c petre-c deleted the fix/nullable-warnings branch August 4, 2025 19:42
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

Comments