Closed lambdabaa closed 10 years ago
This issue was introduced when we upgraded meteor from 0.7.2 to 0.8.0 in f1aca1367571a8429e4ae51a5c49b84ff12469ed. The new "blaze" rendering engine is less forgiving than the old "spark" rendering engine. The stray }
that is causing this issue has been around since 0.0.1 (see https://github.com/gaye/envoy/blob/e75882fa3fba4fcef076daced558c57a61511d9b/app/client/templates/decks.html#L16).
At f1aca1367571a8429e4ae51a5c49b84ff12469ed they include a rogue
}
character at the end of the deckname.