Skip to content

Issues: mxriverlynn/backbone.memento

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

12 Open 0 Closed
12 Open 0 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Restoring collection creates new model instances
#27 opened Dec 27, 2023 by Grid405
model with sub models or collections
#24 opened Jan 7, 2016 by linus-amg
Rebasing memento on current state
#23 opened Aug 29, 2014 by StevenLangbroek
4
NPM Package
#22 opened Jul 20, 2014 by stayradiated
AMD shim, please?
#20 opened Mar 6, 2014 by dminkovsky
1
[enhancement] Add missing bower.json.
#17 opened Jan 7, 2014 by timgluz
Getting total list size and current index
#16 opened Dec 23, 2013 by Ratikant01
1
unsetting attributes during restore/restart conflicts with backbone validation
#14 opened Aug 1, 2012 by adamlangsner
1
nested arrays/objects
#13 opened Jul 13, 2012 by KidkArolis
How about a changed?
#12 opened May 15, 2012 by deitch
change event does not know if it originated from Memento
#6 opened Nov 1, 2011 by rockymeza
3
support named states, and only storing / restoring certain attributes
#5 opened Oct 8, 2011 by mxriverlynn
2
ProTip! Type g i on any issue or pull request to go back to the issue listing page.