-
Notifications
You must be signed in to change notification settings - Fork 185
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
FeedFetcher: Use feeds logo instead of the favicon #1164
Conversation
I think this should also have a unittest associated with it. |
Not sure if that's good idea to use it as the favicon in front of a feed. According to the Atom standard the logo has the aspect ratio of 2:1 and the RSS standard seems to also prefer a non-square image. |
@anoymouserver I doubt that anyone adheres to it, the only feed I found didn't it was simply the wordpress 32x32 favicon |
I would also love to increase the size of the favicons we can pull, but thats not supported by the lib |
Wouldn't it be better then to extend the 3rd-party lib to prefer higher resolutions (or even better SVGs) (ArthurHoaro/favicon#12)? |
I think I would prefer that, as it would bring an improvement to almost all feeds. |
Could we check if the feed's logo is square and if not, just use the favicon? |
@anoymouserver sounds good I will check how to do that. |
Do we want to check the aspect ratio every time we build the feed, like this? If yes I will try to fix the unit tests |
I will manually squash the commits before merging |
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.
Just some nitpicks. Feature looks good.
Codecov Report
@@ Coverage Diff @@
## master #1164 +/- ##
============================================
- Coverage 91.34% 90.96% -0.39%
- Complexity 662 665 +3
============================================
Files 57 57
Lines 2358 2369 +11
============================================
+ Hits 2154 2155 +1
- Misses 204 214 +10
Continue to review full report at Codecov.
|
The logo of the feed is prefered if it is a square picture, else the favicon is returned. Signed-off-by: Benjamin Brahmer <[email protected]> Co-authored-by: Sean Molenaar <[email protected]>
Changed - Remove outdated item DB code. ( #1056) - Stop returning all feeds after marking folder as read. (#1056) - Always fetch favicon (#1164) - Use feed logo instead of favicon if it exists and is square (#1164) - Add CI for item lists (#1180) Fixed - Item list throwing error for folder and "all items" (#1180) - Articles with high IDs can be placed lower than articles with low IDs (#1147) - Feeds are accidentally moved on rename (#1189) - Item list not using ID for offset (#1188) Signed-off-by: Benjamin Brahmer <[email protected]>
Changed - Remove outdated item DB code. ( #1056) - Stop returning all feeds after marking folder as read. (#1056) - Always fetch favicon (#1164) - Use feed logo instead of favicon if it exists and is square (#1164) - Add CI for item lists (#1180) Fixed - Item list throwing error for folder and "all items" (#1180) - Articles with high IDs can be placed lower than articles with low IDs (#1147) - Feeds are accidentally moved on rename (#1189) - Item list not using ID for offset (#1188) Signed-off-by: Benjamin Brahmer <[email protected]>
Changed - Remove outdated item DB code. ( nextcloud#1056) - Stop returning all feeds after marking folder as read. (nextcloud#1056) - Always fetch favicon (nextcloud#1164) - Use feed logo instead of favicon if it exists and is square (nextcloud#1164) - Add CI for item lists (nextcloud#1180) Fixed - Item list throwing error for folder and "all items" (nextcloud#1180) - Articles with high IDs can be placed lower than articles with low IDs (nextcloud#1147) - Feeds are accidentally moved on rename (nextcloud#1189) - Item list not using ID for offset (nextcloud#1188) Signed-off-by: Benjamin Brahmer <[email protected]> Signed-off-by: Marco Nassabain <[email protected]>
Changed - Remove outdated item DB code. ( nextcloud#1056) - Stop returning all feeds after marking folder as read. (nextcloud#1056) - Always fetch favicon (nextcloud#1164) - Use feed logo instead of favicon if it exists and is square (nextcloud#1164) - Add CI for item lists (nextcloud#1180) Fixed - Item list throwing error for folder and "all items" (nextcloud#1180) - Articles with high IDs can be placed lower than articles with low IDs (nextcloud#1147) - Feeds are accidentally moved on rename (nextcloud#1189) - Item list not using ID for offset (nextcloud#1188) Signed-off-by: Benjamin Brahmer <[email protected]> Signed-off-by: Marco Nassabain <[email protected]>
Changed - Remove outdated item DB code. ( nextcloud#1056) - Stop returning all feeds after marking folder as read. (nextcloud#1056) - Always fetch favicon (nextcloud#1164) - Use feed logo instead of favicon if it exists and is square (nextcloud#1164) - Add CI for item lists (nextcloud#1180) Fixed - Item list throwing error for folder and "all items" (nextcloud#1180) - Articles with high IDs can be placed lower than articles with low IDs (nextcloud#1147) - Feeds are accidentally moved on rename (nextcloud#1189) - Item list not using ID for offset (nextcloud#1188) Signed-off-by: Benjamin Brahmer <[email protected]> Signed-off-by: Marco Nassabain <[email protected]>
Changed - Remove outdated item DB code. ( nextcloud#1056) - Stop returning all feeds after marking folder as read. (nextcloud#1056) - Always fetch favicon (nextcloud#1164) - Use feed logo instead of favicon if it exists and is square (nextcloud#1164) - Add CI for item lists (nextcloud#1180) Fixed - Item list throwing error for folder and "all items" (nextcloud#1180) - Articles with high IDs can be placed lower than articles with low IDs (nextcloud#1147) - Feeds are accidentally moved on rename (nextcloud#1189) - Item list not using ID for offset (nextcloud#1188) Signed-off-by: Benjamin Brahmer <[email protected]>
This changes the behavior of fetching the favicon, since feed-io offers to get the feeds logo, we try to get that first, then fall back to the favicon.
I didn't change the var name, I'm not sure if we should do that. But that would include API changes if I'm not wrong.
Also I want to test this first.