Add summary field to the build-in atom parsing
#192
Merged
+20
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cognition9144
force-pushed
the
atom-summary
branch
from
26102f9 to
03ed557
Compare
|
Awesome, thanks! Mind just reverting |
cognition9144
force-pushed
the
atom-summary
branch
from
03ed557 to
6c8a163
Compare
Sure. Just in case it was out of sync. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
According to the atom spec, there's a
summaryfield. Some existing atom feeds provide only thesummaryfield rather than thecontentfield. However, that doesn't violate the spec. And it's hard to urge every feed to provide acontentfield. Ifrss-parserdoesn't parsesummary, it might result in feeds with no real contents. I want to upstreamize it because this is not a problem of a special use case.Related issue: yang991178/fluent-reader#143