Shyam Mahanta
Shyam Mahanta
[Screencast from 25-07-22 07:31:38 PM IST.webm](https://user-images.githubusercontent.com/63530626/180795885-9de4a7ff-dfa0-4c49-981d-7808e9d11121.webm) this issue isnt solved i guess.
yes that was what i tried to show there. I think we dont make the call when user goes into a play but if user landing directly on a play...
i wonder how this can be an issue from a package since filtering with tags doesnt even make any graphql call. thus i think its more of a issue of...
thanks for noticing it. @koustov will be up there to fix it.
yes i checked yesterday and found the issue. its coming from processor.js and line number 101 where code is trying to push something inside an object instead of an array....
is this being take care?
yeah but we are again ending up making the plays call on the homepage. i think we do the sorting thing backend and send most liked plays on same graphql...
oh yes query has be changed also. i also agree for both to be different. trending plays can be measured from page views or using some different mechanism if there.
disabling SW on prod is just to test if the flickering issue is gone or not. as we see the issue is gone but this PR is not yet intended...