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

Add scenario duplication functionality, add copy icon #182

Merged
merged 3 commits into from
Aug 17, 2023

Conversation

e-halinen
Copy link
Collaborator

How to test:

  • Pull branch , npm install, npm start
  • Click the duplication button next to scenario on the scenario list
  • That scenario should be duplicated, settings transferred and name changed to original name + shortened unique UUID of the new scenario (in this case the duplicate)

@e-halinen e-halinen self-assigned this Jun 15, 2023
@e-halinen e-halinen linked an issue Jun 15, 2023 that may be closed by this pull request
@e-halinen e-halinen requested a review from johpiip June 15, 2023 13:41
@hsl-petrhaj hsl-petrhaj self-requested a review June 27, 2023 12:59
Copy link
Contributor

@hsl-petrhaj hsl-petrhaj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Works fine, but please pull before merging.

@johpiip
Copy link
Contributor

johpiip commented Aug 17, 2023

@hsl-petrhaj has approved, so you can go ahead and pull latest changes from master and then merge this branch, @e-halinen. 😊

@johpiip johpiip removed their request for review August 17, 2023 08:01
@e-halinen e-halinen merged commit 58ac16b into master Aug 17, 2023
2 checks passed
@e-halinen e-halinen deleted the 169_duplicate_scenario branch August 17, 2023 10:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Scenario duplication
3 participants