can.Mustache is converting a can.Model to a can.Map #892

Closed
alexisabril opened this Issue Apr 19, 2014 · 3 comments

Comments

Projects
None yet
3 participants
@alexisabril
Contributor

alexisabril commented Apr 19, 2014

I'm not 100% if this is a true bug or just a mis-implementation on my part, however dynamically passing a model(not the instance of a model) to a component is an issue.

http://jsfiddle.net/2mVQh/

I would expect to be able to dynamically pass in a model, such as "User" to a component, then call findAll internally(for generic list components, etc).

@justinbmeyer

This comment has been minimized.

Show comment
Hide comment
@justinbmeyer

justinbmeyer Apr 25, 2014

Contributor

Somewhat related to #450

Contributor

justinbmeyer commented Apr 25, 2014

Somewhat related to #450

@justinbmeyer justinbmeyer added this to the 2.1.0 milestone Apr 25, 2014

@andykant andykant assigned andykant and unassigned andykant Apr 28, 2014

@andykant

This comment has been minimized.

Show comment
Hide comment
@andykant

andykant Apr 30, 2014

Contributor

This ended up not really being related to #450, it has to do with how components handle scope, which is different than how mustache does it.

Contributor

andykant commented Apr 30, 2014

This ended up not really being related to #450, it has to do with how components handle scope, which is different than how mustache does it.

@justinbmeyer justinbmeyer self-assigned this May 3, 2014

@justinbmeyer

This comment has been minimized.

Show comment
Hide comment
@justinbmeyer

justinbmeyer May 3, 2014

Contributor

It was related. I wrote a test, it was breaking and I pulled in yours and it works. can.Component uses can.compute.read.

Contributor

justinbmeyer commented May 3, 2014

It was related. I wrote a test, it was breaking and I pulled in yours and it works. can.Component uses can.compute.read.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment