I already tried this suggestion and had a number of issues with parseModel.
The biggest being that it seems to only apply to the CRUD methods
of a model, and not when you instantiate one directly with attributes.
I need to be able to leverage other Map/Model related features of
CanJS, such as:
These features should work on Models as well as Maps (I am
assuming due to inheritance).
As stated before, the solution I posted does work, (Demo), I just
wanted to know if it could pose any side effects since this effort
feels a bit low-level and edge-case.