Use UTF-8 Encoding Without BOM by Default in All Serializers

[axunonb]

Summary:
Changed the default encoding for all serializers to UTF-8 without BOM (new UTF8Encoding(false)). This ensures compatibility with iCalendar consumers that do not support BOM and provides consistent encoding across all serialization operations.

Affected serializers:
All serializers inheriting from SerializerBase, ComponentSerializer, EncodableDataTypeSerializer, or DataTypeSerializer now default to UTF-8 without BOM unless an explicit encoding is provided.

• Directly from SerializerBase:

  • SimpleDeserializer
  • ComponentSerializer
  • DataMapSerializer
  • DataTypes.DataTypeSerializer
  • DataTypes.DateTimeSerializer
  • DataTypes.DurationSerializer
  • GenericListSerializer
  • ParameterSerializer
  • PropertySerializer

• From ComponentSerializer:

  • CalendarSerializer
  • EventSerializer
  • SerializerFactory

• From EncodableDataTypeSerializer or DataTypeSerializer:

  • DataTypes.AttachmentSerializer
  • DataTypes.EnumSerializer
  • DataTypes.GeographicLocationSerializer
  • DataTypes.IntegerSerializer
  • DataTypes.PeriodListSerializer
  • DataTypes.PeriodSerializer
  • DataTypes.RecurrencePatternSerializer
  • DataTypes.StringSerializer
  • DataTypes.UriSerializer
  • DataTypes.UtcOffsetSerializer
  • DataTypes.WeekDaySerializer

Rationale:
Ensures all iCalendar output is encoded in UTF-8 without BOM by default, as required by many consumers.

Resolves #823

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

❌ Your project status has failed because the head coverage (68%) is below the target coverage (80%). You can increase the head coverage or adjust the target coverage.

@@         Coverage Diff         @@
##           main   #827   +/-   ##
===================================
  Coverage    68%    68%           
===================================
  Files       106    106           
  Lines      4216   4217    +1     
  Branches    941    942    +1     
===================================
+ Hits       2849   2850    +1     
  Misses     1039   1039           
  Partials    328    328           

Files with missing lines	Coverage Δ
Ical.Net/Serialization/SerializerBase.cs	53% <100%> (+2%)	⬆️

🚀 New features to boost your workflow:

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

[minichma]

Not sure, I understand this correctly. As the method is only invoked from test cases, this only makes a difference when invoked from externally if omitting the encoding, right? Doesn't this also affect all the places where serialization is triggered internally? Were searching for UTF8 throughout the code base and found 17 matches. Do they require individual attention?

[axunonb]

this only makes a difference when invoked from externally

Yes. Without an encoding parameter we use UTF8 without BOM for serialization (writing).

Doesn't this also affect all the places where serialization is triggered internally

Yes, as far as writing is concerned. For reading, BOM-handling is transparent by .Net.

UTF8 throughout the code base and found 17 matches

All where writing is concerned should be covered.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud