Enables the parsing of elements defined in another namespace in Person constructs#91
Merged
andy128k merged 1 commit intorust-syndication:masterfrom Sep 14, 2025
Merged
Conversation
Contributor
Author
|
Wanted to follow up on this—please let me know if you'd like any changes! |
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
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 1.0 spec, foreign markup may be processed as children of
atom:entry,atom:feed, or a Person construct. atom-syndication processes extensions inentryandfeedbut ignores foreign markup in Person elements.This PR extends the current handling of extensions to
Person. I've tried to keep the API consistent, but please let me know if you'd like changes.Use case: I am parsing arXiv atom entries, which include an
affiliationelement like this: