APIShortDate type for yyyy-MM-dd date formats #193
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.



This pull request introduces a new custom date type,
APIShortDate, to enforce strict handling of API date fields in theyyyy-MM-ddformat. The main changes include implementing this type, updating relevant data structures to use it, and adding comprehensive tests to ensure correct parsing and formatting.API Date Handling Improvements:
APIShortDatetype incommon/apishortdate.gothat supports only theyyyy-MM-ddformat, with custom JSON marshal/unmarshal logic to reject other date/time formats.InstrumentDatastruct'sDateOfSignaturefield ininstruments/nas/instuments.goto use*common.APIShortDateinstead of*time.Time, ensuring only valid short dates are accepted.Test Coverage Enhancements:
test/apishortdate_test.gocovering valid/invalid formats, round-trip marshalling, and edge cases forAPIShortDate.APIShortDatetype, including changes ininstruments/nas/client_test.goandtest/instruments_test.go. [1] [2] [3]Codebase Cleanup:
timeininstruments/nas/instuments.gosince date handling is now abstracted byAPIShortDate.