Skip to content

Conversation

bbolli
Copy link
Contributor

@bbolli bbolli commented Apr 22, 2024

After trying to parse the first JSON feed I found in the wild [1], I realized that the content element should be a list. This series fixes this defect and prefers HTML content over text.

[1] https://leahneukirchen.org/trivium/index.json

bbolli added 4 commits April 22, 2024 12:55
The spec allows to have both text and HTML elements, and the feedparser
content key supports different content types.

Adjust the code to look at both source elements and add all that are
present.

Signed-off-by: Beat Bolli <dev@drbeat.li>
HTML has generally more useful information than text, so let's move it
first in the content list. Users that want text can still iterate over
the list and pick the text type.

Signed-off-by: Beat Bolli <dev@drbeat.li>
The spec says that at least one element is mandatory. Verify this and
raise an exception if both are missing.

Signed-off-by: Beat Bolli <dev@drbeat.li>
Signed-off-by: Beat Bolli <dev@drbeat.li>
@bbolli
Copy link
Contributor Author

bbolli commented Jun 3, 2024

Ping?

@bbolli
Copy link
Contributor Author

bbolli commented Apr 28, 2025

Ping again? This is now pending since one year...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant