feat(plugin): add ICS plugin with 2 sources (from file or url)

[samber]

No description provided.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 69.20%. Comparing base (b533d82) to head (a8faab9).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #155      +/-   ##
==========================================
+ Coverage   69.17%   69.20%   +0.03%     
==========================================
  Files          76       76              
  Lines        9485     9485              
==========================================
+ Hits         6561     6564       +3     
+ Misses       2839     2837       -2     
+ Partials       85       84       -1     

Flag	Coverage Δ
unittests	69.20% <ø> (+0.03%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[claude]

📋 PR Review Summary

This is a well-implemented ICS/iCal plugin that adds comprehensive calendar parsing capabilities to the ro ecosystem. The implementation follows the established patterns and provides both file and URL-based calendar reading.

✅ Strengths

• Clean API Design: Simple, intuitive interface with NewICSFileReader() and NewICSURLReader()
• Comprehensive Documentation: Excellent examples, error handling documentation, and real-world usage patterns
• Proper Test Coverage: Good test cases covering success scenarios, empty inputs, and error conditions
• Integration: Follows existing plugin patterns and integrates well with the codebase
• Practical Examples: Documentation includes realistic use cases and transformation pipelines

🔧 Issues to Address

1. Resource Management: File handles use defer inside the loop, which could lead to resource leaks
2. Security Documentation: URL function lacks security considerations documentation for server-side use
3. TODO Cleanup: Remove TODO comment from production code or create proper tracking issue

📝 Recommendations

• Consider adding URL validation options for security-conscious environments
• Document the Go 1.20 requirement more prominently
• Consider adding timeout/size limit configuration options in future versions
• Remove the documentation warning that suggests the docs are incomplete

🎯 Overall Assessment

This is a high-quality plugin that will be valuable for users working with calendar data. The implementation is solid, documentation is excellent, and it follows project conventions well.

Status: ✅ Approve with minor suggestions