# Extend undo levels - or snapshot support

**URL:** <https://discourse.nodered.org/t/extend-undo-levels-or-snapshot-support/10509>\
**Category:** Feature Requests\
**Created:** [24 April 2019 15:16 UTC](https://discourse.nodered.org/t/extend-undo-levels-or-snapshot-support/10509 "2019-04-24T15:16:52Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![moebius](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/moebius/32/2872_2.png) [@moebius](https://discourse.nodered.org/u/moebius)\
**Post date:** [24 April 2019 15:16 UTC](https://discourse.nodered.org/t/extend-undo-levels-or-snapshot-support/10509/1 "2019-04-24T15:16:52Z")

</div>

Currently, it is only possible to undo changes until the last deployment.

It would be nice, if this limit could be extended.  
Another possibility would be the support of tab-wise snapshots.

Use case: trying something with many changes and/or deployments.

---

<div class="post-metadata">

**Author:** ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)\
**Post date:** [24 April 2019 15:27 UTC](https://discourse.nodered.org/t/extend-undo-levels-or-snapshot-support/10509/2 "2019-04-24T15:27:20Z")

</div>

Take a look at the projects feature...

> **[Version 0.18 released](https://nodered.org/blog/2018/01/31/version-0-18-released)**
>
> Find out more on the blog

---

<div class="post-metadata">

**Author:** ![moebius](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/moebius/32/2872_2.png) [@moebius](https://discourse.nodered.org/u/moebius)\
**Post date:** [24 April 2019 15:36 UTC](https://discourse.nodered.org/t/extend-undo-levels-or-snapshot-support/10509/3 "2019-04-24T15:36:20Z")

</div>

Thanks, i'm aware of the project feature - but it's a little more complicated than pressing "Ctrl-Z" 🙂

Sure, i could also copy the tab and disable the original, but the easiest way are a few keystrokes to restore the old state.

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [24 April 2019 17:46 UTC](https://discourse.nodered.org/t/extend-undo-levels-or-snapshot-support/10509/4 "2019-04-24T17:46:11Z")

</div>

> [@moebius](#):
>
> Thanks, i'm aware of the project feature - but it's a little more complicated than pressing "Ctrl-Z" 🙂

But equally, why would we implement a parallel system that duplicated what projects can do, but without the same level of functionality?

I think there is a place for a more simplified user experience with projects - something I posted back in January: [Feedback wanted: Simplified git workflow](https://discourse.nodered.org/t/feedback-wanted-simplified-git-workflow/7286)

---

<div class="post-metadata">

**Author:** ![moebius](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/moebius/32/2872_2.png) [@moebius](https://discourse.nodered.org/u/moebius)\
**Post date:** [24 April 2019 18:07 UTC](https://discourse.nodered.org/t/extend-undo-levels-or-snapshot-support/10509/5 "2019-04-24T18:07:03Z")

</div>

If the simplified workflow runs completely local without the usual project overhead, it sounds like a good idea!

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [24 April 2019 18:28 UTC](https://discourse.nodered.org/t/extend-undo-levels-or-snapshot-support/10509/6 "2019-04-24T18:28:25Z")

</div>

What do you define the 'usual project overhead' as?

Projects can run completely locally already. There is no requirement to have a remote repository.

---

<div class="post-metadata">

**Author:** ![moebius](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/moebius/32/2872_2.png) [@moebius](https://discourse.nodered.org/u/moebius)\
**Post date:** [24 April 2019 18:52 UTC](https://discourse.nodered.org/t/extend-undo-levels-or-snapshot-support/10509/7 "2019-04-24T18:52:35Z")

</div>

- username / password
- naming and definition of the project
- naming of commit msgs

All this should be autogenerated / filled.

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [24 April 2019 19:32 UTC](https://discourse.nodered.org/t/extend-undo-levels-or-snapshot-support/10509/8 "2019-04-24T19:32:59Z")

</div>

If you only have a local project with no remote, there is no username/password.

You need to create a project to get started. It's a 10 second task to give it a name. Sorry, I don't think that's overhead - it's a quick one off task needed to get the benefits projects bring.

See the thread I linked to regarding commit messages. If you have any suggestions as to how those auto-filled commit messages could be made useful, I'd appreciate your input.

---

<div class="post-metadata">

**Author:** ![moebius](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/moebius/32/2872_2.png) [@moebius](https://discourse.nodered.org/u/moebius)\
**Post date:** [24 April 2019 20:10 UTC](https://discourse.nodered.org/t/extend-undo-levels-or-snapshot-support/10509/9 "2019-04-24T20:10:20Z")

</div>

About the commit msg: I would include the changed flow name(s) and a timestamp in the comment.

Also i'm wondering, how easy it is to go back to a previous version? And if there is only one flow changed, will only this flow redeployed or all from the project?