Oh, shoot, you’re totally right 
. We just fixed that exact error further down in the file (you can see the whole story in this thread), but it looks like we missed that one.
I’ve put in an internal bug ticket and it should be a very quick fix. We’ll report back when it’s out. So sorry about that!