Just going to leave this horror here. It's the post feed logic from Tesseract that determines what posts should be displayed or hidden.
If that's horror to you, you've been sheltered. That's quite readable, though I'd make the long lines into their own subroutines.
Delightfully devilish, indeed. You made it as easy to read as possible though.
Why not factor out the
!via de Morgan's laws (which would also remove most of the parentheses, as iirc&&binds tighter than||)? Also, does that language have a{#continue}sort of syntax for loops? If so, you could make it a guard clause.Thank you, I knew the rule but did not know it had a name.
What is that, Vue?
So clearly that language has support for methods in this context and it isn't necessary for all this logic to be mixed in with the markup. So my initial comment on this PR would be "please create a method isPostVisibleForUser(post_id, user_id)". That method could be moved to a service related to post visibility, because this seems like a common feature. Though from my experience with Angular, common features are often pulled in as whole components with markup and all, so it could be fine to couple them.
Early returns save lives
But what if I were to add more 'and'
It would be extremely painful
You’re a big function
For you
That's why you set the alternate/exit cases as individual if statements before whatever was going to be inside the original if block.
To me too long to learn that.
Gotta go fast
