Pool navigation & listing improvements - #732
Conversation
this implementation was *heavily* cherry-picked from PR rr-#403.
Update stylus for :has support
We were always using the first pool the current post belongs to.
This was very slow when any entry was unavailable, such as on single-post pools, or edges of pools (first/last post). Also only fetch id. Previously it would get the thumbnail url.
a0174fc to
382239f
Compare
Can still be cleaned up some more. Need to compare speed of the get_around query vs nearby pool posts.
Same as posts in search results.
5c7b266 to
64c3a6e
Compare
|
Good catch. I'll account for this in a later commit, for now reverting ff788a5 should fix it. But that is the commit that improves pool listing loading performance, lol. |
|
Can confirm reverting ff788a5 fixes both issues. |
|
I know I'm technically necroposting, but the issue of In client/js/models/pool.js Which allow the code to find the correct functions, this is purely a quick fix that I haven't had time to thoroughly test so please be incredibly careful if setting this up on a large production instance |

Building upon #537 with some aspects from #403.
Has been in use for about two years on a mid-sized public instance.
Notable changes new to this PR:
TODO list:
Notes:
Post navigation override seems redundant, we can just have sort:pool in the pool navigator's search links? Should lead to the same sorting.