v5.3.0

Breaking Change

SchemaDateRange.Start and .End changed from string to DateTimeOffset (Issue #21)

DatasetRange already used DateTimeOffset for its Start/End properties, but SchemaDateRange (used in DatasetRange.RangeBySchema) was using raw strings. This inconsistency meant consumers had to manually parse dates to do comparisons or arithmetic.

What changed

• SchemaDateRange.Start: string → DateTimeOffset
• SchemaDateRange.End: string → DateTimeOffset
• Added SchemaDateRange.Duration computed property (matches DatasetRange.Duration)

How to fix if affected

If your code assigned SchemaDateRange.Start or .End to a string variable:

// Before (v5.2.x)
string start = schemaRange.Start;

// After (v5.3.0)
string start = schemaRange.Start.ToString("o");  // ISO 8601
// Or better — just use DateTimeOffset directly
DateTimeOffset start = schemaRange.Start;

Other changes

• [JsonIgnore] added to Duration on both DatasetRange and SchemaDateRange to prevent serialization leakage
• Cleaned up .sln file: removed 23 gitignored project references that showed as absent for public repo clones (Issue #19 follow-up)