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
We are modeling the content:encoded for the <item> nodes, but not for the <channel> nodes. That's not great, because many podcasts use it (e.g., src/test/resources/xml/real-life-feeds/reply-all.xml). We should add a PodcastContent.
The text was updated successfully, but these errors were encountered:
I have done this but it is a breaking change both in terms of source and binary compatibility. I can create a 2.0.0 branch once #95 is merged, and we can consider shipping 1.1.0 since it has a meaty set of changes as it is already. What do you think @mpgirro?
We are modeling the
content:encoded
for the<item>
nodes, but not for the<channel>
nodes. That's not great, because many podcasts use it (e.g.,src/test/resources/xml/real-life-feeds/reply-all.xml
). We should add aPodcastContent
.The text was updated successfully, but these errors were encountered: