Skip to content
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.

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

CHE-5333. Mark editor state as dirty after undo/redo operations #5408

Merged
merged 1 commit into from
Jun 22, 2017

Conversation

RomanNikitenko
Copy link
Member

What does this PR do?

We have incorrect dirty state for editor at undo/redo operations and it leads to some bugs related to unsaved data.
So we need to track these operations and set a corresponding dirty state for editor.

What issues does this PR fix or reference?

#5333

Changelog

Mark editor state as dirty after undo/redo operations

Release Notes

Mark editor state as dirty after undo/redo operations

Docs PR

Don't need. It's a bug fix.

Signed-off-by: Roman Nikitenko rnikitenko@redhat.com

Signed-off-by: Roman Nikitenko <rnikitenko@redhat.com>
@RomanNikitenko RomanNikitenko added status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. and removed status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. labels Jun 20, 2017
@codenvy-ci
Copy link

@RomanNikitenko RomanNikitenko merged commit 2156886 into master Jun 22, 2017
@slemeur
Copy link
Contributor

slemeur commented Jun 22, 2017

Where are :

  • labels
  • milestone
  • and PM review

@RomanNikitenko RomanNikitenko added this to the 5.14.0 milestone Jun 22, 2017
@RomanNikitenko RomanNikitenko deleted the CHE-5333 branch June 22, 2017 08:48
@RomanNikitenko RomanNikitenko added the kind/bug Outline of a bug - must adhere to the bug report template. label Jun 22, 2017
@RomanNikitenko
Copy link
Member Author

@slemeur I've set label and milestone - thank you!
Do we need PM review for a bug fix?

@vparfonov
Copy link
Contributor

@slemeur What you want review here?

@slemeur
Copy link
Contributor

slemeur commented Jun 22, 2017

It is ok now. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Outline of a bug - must adhere to the bug report template.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants