Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Bring back Map::coerceLayer() #102
@tmcw, this one is still biting us in the ass. I get that major revision numbers should be expected to break code, but there are still examples broken in alpha and the errors causes are totally cryptic and difficult to track down—especially if you're not familiar with the code.
I really liked the flexibility that the old coercion behavior provided. Removing it breaks a bunch of our examples, all of the code in gh-pages, and several projects we're working on that benefit greatly from using the bleeding edge MMJS.
Can we bring it back, please?
This comment has been minimized.
This comment has been minimized.Show comment Hide comment
I can work on a proper implementation of TemplatedLayer, better error reporting, and fixing examples, but really want to see if there's a way to have a 'layers in, layers out' expectation. Also, coerceLayer could be a Modest Maps utility if that makes things easier to port.