You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a feed item entry has both an <itunes:summary> tag and a <description> tag, the <itunes:summary> tag takes precedence and overwrites whatever is present in the <description> tag, making it available at the summary key on the item's dict.
My expectation is that the <itunes:summary> value would be available at the itunes_summary key, much like the other values in the iTunes namespace and the <description> tag's value would be available at summary as outlined in the documentation. Instead the iTunes summary is given precedence as shown above and applied to the summary key. Even when the <itunes:summary> is an empty tag, I still get an empty string as opposed to the value from the <description> field.
This seems to be very similar to both #314 and #316. Is this expected behavior or is this a bug?
The text was updated successfully, but these errors were encountered:
When a feed item entry has both an
<itunes:summary>
tag and a<description>
tag, the<itunes:summary>
tag takes precedence and overwrites whatever is present in the<description>
tag, making it available at thesummary
key on the item's dict.Example:
Parsing the above with
parse()
, thesummary
for the item entry is set to the value in<itunes:summary>
:My expectation is that the
<itunes:summary>
value would be available at theitunes_summary
key, much like the other values in the iTunes namespace and the<description>
tag's value would be available atsummary
as outlined in the documentation. Instead the iTunes summary is given precedence as shown above and applied to thesummary
key. Even when the<itunes:summary>
is an empty tag, I still get an empty string as opposed to the value from the<description>
field.This seems to be very similar to both #314 and #316. Is this expected behavior or is this a bug?
The text was updated successfully, but these errors were encountered: