CanJS tries to parse JSON-map which contains a dot in the key

[ghost]

My rest service return a map of key-value pairs. The key may contain dots. If I try to access this with can.Model an exception is thrown:

Uncaught can.Observe: Object does not exist can.jquery.js:695
can.Observe.can.Construct._set can.jquery.js:695
can.Observe.can.Construct._attrs can.jquery.js:792
can.Observe.can.Construct.attr can.jquery.js:607
can.Observe.can.Construct.setup can.jquery.js:588
can.extend.newInstance can.jquery.js:270
Constructor can.jquery.js:350
hookupBubble can.jquery.js:446
can.Observe.can.Construct.__set can.jquery.js:715
can.Observe.can.Construct._set can.jquery.js:693
can.Observe.can.Construct.attr can.jquery.js:614
can.Model.can.Observe.models can.jquery.js:1317
can.each can.jquery.js:45
can.Model.can.Observe.models can.jquery.js:1315
d.abort can.jquery.js:1054
jQuery.extend.Deferred.promise.then.jQuery.Deferred.fns jquery.js:1059
jQuery.Callbacks.fire jquery.js:910
jQuery.Callbacks.self.fireWith jquery.js:1020
done jquery.js:7234
jQuery.ajaxTransport.send.callback jquery.js:7926

If I remove the dots it works. Here's an example of the JSON message which leads to the error:

{"key.1":"value1","key.2":"value2 "}

Any idea if this is a CanJS bug or how I could solve this problem?

[daffl]

This is the same as issue #257. Maybe the workaround mentioned there works for you, too? A fix for this should definitely be part of 1.2

[ghost]

Yes, I have noticed afterwards that issue #257 is probably related. The workaround also worked for me, and then I can access the attributes using result.__get('key.1').
A fix for this would be great.
Thank you