-
Notifications
You must be signed in to change notification settings - Fork 52
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
iTunes extension not working while the extensions map does contain the respective information #158
Comments
Extensions are recognized by a namespace URI. iTunes URI in your example is |
Wouldn't a toLowercase comparison solve the issue? |
If you'd like to I can add a pull request for this. @andy128k |
Tough question. Formally URIs are case sensitive and such a change may be risky. |
Good point. The question is will someone else create a schema that is equal to the iTunes url but change a character in the url to lower/uppercase. Probably not. So I think the chance of breaking an existing project using your library is very minimal. |
https://help.apple.com/itc/podcasts_connect/#/itcb54353390
It's not about someone creating a schema (that's unlikely and that should be someone with access to But someone may create a feed with multiple namespaces:
Now we have an issue with merging formally two extensions into a single one. OTOH someone may create an alias like I'd say, this is much bigger issue than just add |
So, I reviewed the code and it seems that I overestimated the complexity. It looks a bit easier now #159. |
Thank you for the changes 😃. |
I use your crate which works really smooth in one of my projects: SamTV12345/PodFetch#492 . Unfortunately the itunes extension doesn't work with one of the podcasts a user tried to download. Maybe you have an idea why the extensions map is filled with the image tag while the itunes_extensions shows None.
I created a reproducible here: https://gitlab.com/samtv12345/rss-crate-bug-report. Just run cargo run and you should see that itunes extension is none while the map contains the information. Do you have an idea why @andy128k ?
The text was updated successfully, but these errors were encountered: