pull down to refresh

Hahahaha I have no clue where to start but I’ll give it a shot
77 sats \ 14 replies \ @ek 30 Mar
Start with understanding the problem the ticket is describing
reply
Understanding is one thing fixing it is whole other skill set I am still developing. Like I have no clue where this issue exists in the code base. Plus it’s marked as a ui/UX bug but how do I know it’s not a back end issue?
reply
649 sats \ 12 replies \ @ek 30 Mar
reply
Now I understand the bug the sat counter per zap is missing. It should be before replies but it’s missing on this comment for some odd reason
reply
106 sats \ 9 replies \ @ek 31 Mar
it's because it's pinned, see #707679 (comment link) vs #707679 (direct link)
reply
yep i noticed pinned comments don't show the amount of zaps, and doesn't even let me zap by clicking the lightning bolt as usual. This should probably be changed.
And @BlokchainB, my suggestion for where to start in the code is to look for the logic of pinned comments (search pinned or pin in Github)... that's where I would start, anyway.
😆😆😆😆
reply