Implicit linking between trail maps?

I was starting to go through and check off items I had completed on the trail maps when I noticed there seems to be an implicit connection between items that share a title across different trail maps. In particular I noticed checking off

  • Run programs.
  • Avoid syntax errors.
  • Print values.
  • Use common control flow structures.
  • Instantiate an object.
  • Iterate over collections.

in the Ruby trail map also checked those items in the JavaScript trail map, and vice versa. I see those items share ids which seemed strange, but I see that is by design (

Thanks for the heads up on this. This is actually an unintentional bug. They shouldn’t use the same IDs and we’ll have to change them so they are differentiated.

thanks again, and sorry about the trouble,