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

Exporting a playbook that was imported generates a completely new playbook while should consider playbook versioning #15

Open
lucamrgs opened this issue Mar 28, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@lucamrgs
Copy link

When a playbook is imported, modified, and exported, the exported playbook is considered a new playbook altogether.

It would be nice if a prompt asked if the exported playbook should be an update on the imported playbook, and manage the playbook version and related properties (time created, time modified) accordingly.

@mateusdz
Copy link
Contributor

mateusdz commented Apr 2, 2024

Most probably this is happening since the Roaster populates the creator identifier automatically. Therefore, an exported playbook that is imported (in a refreshed/page reloaded) Roaster has a different identifier. Then, you are not creator of this playbook and therefore a new playbook (and a derived from embedded relationship) is created.

(However, recently, I became aware of a bug with the identifier, which may cause confusion on this front as well.)
Leaving this issue open until further investigation with the identifier.

@mateusdz mateusdz added the bug Something isn't working label Apr 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants