-
Notifications
You must be signed in to change notification settings - Fork 179
Implement parsing of the <id> element in OPDS 1.x feeds #655
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement parsing of the <id> element in OPDS 1.x feeds #655
Conversation
9e2b993 to
2b15c8c
Compare
2b15c8c to
07f3a99
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good, thank you. Please note that we will revamp the OPDS models next year, and this kind of information will be available as part of the extension models for metadata instead of a native property.
|
Thanks a lot for merging my PRs, @mickael-menu!
Can I find this written somewhere, such as in the issues? I’m about to submit another PR and don’t want to waste your time reviewing something that isn’t aligned with future plans. |
|
It's not documented anywhere but it should look like the swift-toolkit/Sources/Shared/Publication/Metadata.swift Lines 64 to 71 in 8875768
and the metadata keys will be expanded with the XML namespace, similarly to this with EPUB: swift-toolkit/Tests/StreamerTests/Parser/EPUB/EPUBManifestParserTests.swift Lines 48 to 67 in 8875768
|
The OPDS 1.x is based on Atom, and Atom’s Feed must contain an
idtag. I found it useful to parse the<id>tag.I left it as optional to avoid breaking compatibility with existing clients.