In the PR that added the dateRange feature, the specification
If a Playlist contains two EXT-X-DATERANGE tags with the same ID attribute value, then any AttributeName that appears in both tags MUST have the same AttributeValue.
was misinterpreted as EXT-X-DATERANGE tags with the same ID in a playlist must have the same attributes and same attribute values.
This PR
fixes that by comparing attributes of dateRange tags with the same ID only if both the tags contain the attribute
merges dateRange tags with same IDs if no attribute has conflicting values (This will be useful when parsing SCTE35-IN/OUT pairs)
In the PR that added the dateRange feature, the specification
If a Playlist contains two EXT-X-DATERANGE tags with the same ID attribute value, then any AttributeName that appears in both tags MUST have the same AttributeValue.was misinterpreted asEXT-X-DATERANGE tags with the same ID in a playlist must have the same attributes and same attribute values.This PR