Added #

• parseBoolean property parser for consistent boolean value parsing

Improved #

• Simplified occurrence iterator implementation with better code reuse across component types

Fixes #

• Invalid pubspec.yaml package description

Fixed #

• All README code examples verified to compile and run correctly

Improved #

• Enhanced pubspec.yaml with topics and metadata for improved pub.dev visibility

Changed #

• BREAKING: Renamed inRange() extension methods to occurrences() for consistency
  • All component iterable extensions (EventIterableQuery, TodoIterableQuery, JournalIterableQuery, TimeZoneIterableQuery) now use occurrences()
  • Parameters are now optional: occurrences({CalDateTime? start, CalDateTime? end})
  • Call without parameters to get all occurrences, or provide start/end to filter
• Updated RecurrenceIterator.occurrences() to accept optional start, end, and duration parameters
• Removed RecurrenceIteratorQuery extension - logic consolidated into RecurrenceIterator class

Added #

• isMultiDay extension property on EventComponent and TodoComponent

Fixed #

• inRange() extensions now guarantee chronological ordering across all components
• Date-only end boundary handling in inRange()

Added #

• addDuration extension method on CalDateTime
• isAllDay extension property on EventComponent
• effectiveEnd extension property on EventComponent
• effectiveDuration extension property on Event and Todo components
• inRange() extension method on Iterable

Fixed #

• Ordering of occurrences when combining RRULE and RDATE values
• TodoComponent.dtstart is now nullable (was incorrectly required)
• JournalComponent.dtstart is now nullable (was incorrectly required)
• Documentation comments for several component properties

Improved #

• Refactored RecurrenceIterator for better separation of concerns
• Reorganized extensions into dedicated directory structure
• Major test coverage increase

Fixed #

• Fixed resources property type from List<CalendarUserAddress> to List<String> and use valuesUnion() for RFC 5545 compliance

Improved #

• Significantly increased test coverage

Fixed #

• Updated README examples to use correct API methods (parseComponents instead of deprecated streamComponents)
• Added missing required DTSTAMP properties in README examples for RFC 5545 compliance

Improved #

• Enhanced documentation comments across public APIs for better clarity and consistency

Added #

• RFC 5545 compliant iCalendar parser
• Support for VEVENT, VTODO, VJOURNAL, VTIMEZONE components
• Full RRULE recurrence expansion
• Streaming parser for large files
• Custom property parser registration
• Timezone-aware date/time handling
• Two-layer architecture (document + semantic)