Properties on a can.route.map are coerced to strings when they should not be #2277

Closed
DesignByOnyx opened this Issue Feb 18, 2016 · 2 comments

Comments

Projects
None yet
3 participants
@DesignByOnyx
Contributor

DesignByOnyx commented Feb 18, 2016

I believe this issue is caused by this:

https://github.com/canjs/canjs/pull/2246/files

...and lives in isolation here:

https://jsfiddle.net/ryanwheale/0wyreatk/

@justinbmeyer

This comment has been minimized.

Show comment
Hide comment
Contributor

justinbmeyer commented Feb 18, 2016

@DesignByOnyx DesignByOnyx changed the title from Properties on a can.Map tied to the route are errantly converted to strings to Properties on a can.route.map are coerced to strings when they should not be Feb 18, 2016

@justinbmeyer justinbmeyer added the bug label Feb 18, 2016

@justinbmeyer justinbmeyer added this to the 2.3.17 milestone Feb 18, 2016

@justinbmeyer

This comment has been minimized.

Show comment
Hide comment
@justinbmeyer

justinbmeyer Feb 18, 2016

Contributor

We should only be converting the serialize-able properties.

Contributor

justinbmeyer commented Feb 18, 2016

We should only be converting the serialize-able properties.

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