Skip to content
This repository has been archived by the owner on Mar 20, 2021. It is now read-only.

Avoid instantiating new location objects on navigate #41

Closed
kpdecker opened this issue Sep 2, 2014 · 1 comment
Closed

Avoid instantiating new location objects on navigate #41

kpdecker opened this issue Sep 2, 2014 · 1 comment
Milestone

Comments

@kpdecker
Copy link
Contributor

kpdecker commented Sep 2, 2014

This removes the need to have backbone specific code that reassigns the location value when using pooling.

@kpdecker kpdecker added bug and removed bug labels Sep 2, 2014
@kpdecker
Copy link
Contributor Author

kpdecker commented Sep 2, 2014

Released in 0.11.0

@kpdecker kpdecker modified the milestone: 1.0.0 Feb 13, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

No branches or pull requests

1 participant