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.

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

Jump to bottom

Policy studio: Strange behaviour when add new flow, save and select other flow. #376

Closed
gcusnieux opened this issue Jun 11, 2021 · 1 comment
Closed

Policy studio: Strange behaviour when add new flow, save and select other flow. #376

gcusnieux opened this issue Jun 11, 2021 · 1 comment
Labels
released type: bug

Comments

@gcusnieux
Copy link
Member

Describe the bug
The last flow selected mark as dirty (yellow highlight in menu) after a form submit and save.

To Reproduce
Steps to reproduce the behavior:

  1. Go to "Policy studio AM editable story"
  2. Add new flow
  3. Change the title
  4. Submit the flow form
  5. Save all
  6. Select an other flow

Expected behavior
After step 6, the flow should not mark as dirty

Screenshots

policy-studio-dirty
gcusnieux added a commit that referenced this issue Jun 11, 2021
@gcusnieux
fix(gv-policy-studio): mark flow as dirty only if has changed
15c989d 
fix #376
@gcusnieux gcusnieux mentioned this issue Jun 11, 2021
Merged
gcusnieux added a commit that referenced this issue Jun 14, 2021
@gcusnieux
fix(gv-policy-studio): mark flow as dirty only if has changed
9a851cb 
fix #376
gcusnieux added a commit that referenced this issue Jun 17, 2021
@gcusnieux
fix(gv-policy-studio): mark flow as dirty only if has changed
0c1a06b 
fix #376
@graviteeio
Copy link
Contributor

🎉 This issue has been resolved in version 3.4.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

@leleueri leleueri mentioned this issue Jun 22, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
released type: bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gcusnieux @graviteeio