You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 21, 2024. It is now read-only.
I haven't tested this, but I'd be inclined to fix this by reverting 9ad1c72. It seems nice to not special case too many things that are specific to our team, and I think that would also fix this problem (but I haven't checked to make sure). (Plus not special casing not adding people as spoiled means other things like testsolving will correctly not list any puzzles for you to testsolve.)
On the other hand, we could create a spoiledOnEverything privilege, and then have isSpoiled (or whatever the function is called) check both the regular spoiled thing and spoiledOnEverything.
Hmm, I thought there was at least one page that didn't do that, but the few pages I checked do indeed do that for puzzles I'm already spoiled on. Well, I guess one way of fixing this would be to not black out for spoiled puzzles.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We're spoiled on everything anyway
The text was updated successfully, but these errors were encountered: