-
Notifications
You must be signed in to change notification settings - Fork 181
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
feature request: support for Atom Entry Documents #128
Comments
Given the relative unpopularity of Atom at this point, I'm not sure it would make sense to put development effort into official support for entry documents. However, depending on the specifics, it looks like direct support might not be too hard to work around. Can you upload a couple of the entry documents you're working with? Do you generate these documents (or get them from a source with consistent formatting), or do they come in from a variety of sources? |
Hi @hober, @GarthSnyder 😄 I believe an Atom Entry Document should have a single root node of Support for this should be easy to add. However, I will close this for now, since it's an old issue. If you really need it still, please kindly re-open, and we can take a look on how to add this to the v10 branch. Thank you 🙏 |
It's still something that I'd like to see, but it's your project! :) |
Do you have some samples you could share? |
I have an aging website whose backing store is a whole pile of Atom Entry Documents, and I'd like to replace the Python script that processes them with a Swift program. But it doesn't look like FeedKit supports these documents; I get a
feedNotFound
error when I try to parse one.The text was updated successfully, but these errors were encountered: