krawaller

3 ms·

1. 1.▲
   by krawaller 12y ago

   There's now a follow-up to this post, walking through a refactor based on the comments given here and elsewhere. Thank you all for the feedback! https://news.ycombinator.com/item?id=8273026
2. 2.▲
   Diving deeper into a React.js memory game case study(blog.krawaller.se)

   5 points by krawaller 12y ago|0 comments
3. 3.▲
   by krawaller 12y ago

   Wow, thank you so much for this! Reading through your changes I do feel a bit silly. And wiser! :)
4. 4.▲
   by krawaller 12y ago

   The not doing anything is intentional - only when the pair is resolved and the status row goes back to saying "choose a tile" can you click a new tile. This "feature" really needs to be communicated better though, sorry
5. 5.▲
   by krawaller 12y ago

   I touch on this in a post - I did try the latter, but got a React warning in the console about unmounted components. That, together with a comment in the official docs, made me go with the show/hide approach. Although as pointed out in
6. 6.▲
   by krawaller 12y ago

   Might be I've been sloppy with adding -moz- to some css rules. Will take a look!
7. 7.▲
   by krawaller 12y ago

   Oh, indeed, I've completely missed the classSet plugin! That would indeed make the code more elegant. And fair point about the logic perhaps being too complicated here. Thanx for the pointers!