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

[Feature Request] Lock View / Elements #1105

Open
cadmageren opened this issue Dec 14, 2024 · 1 comment
Open

[Feature Request] Lock View / Elements #1105

cadmageren opened this issue Dec 14, 2024 · 1 comment

Comments

@cadmageren
Copy link

Description

Summary:

Introduce a locking mechanism in Archi to safeguard views and elements, especially in collaborative environments such as CoArchi. This feature aims to prevent accidental modifications or deletions of stable and finalized model components.

Details:

Locking Views:

When a view is locked, it becomes immutable. Users cannot modify or delete the view or any elements contained within it.
Locked views can be unlocked by any user when necessary.

Locking Elements:

A locked element cannot be deleted or modified. However, it can still be moved to another location within the model.

Folder Locking:

Locking a folder applies the lock to all elements and sub-elements within that folder.
Locked folders prevent the movement or modification of their contents unless explicitly unlocked.

Use Case:

This feature helps maintain the integrity of finalized model components, ensuring that no accidental changes or deletions occur. It is particularly beneficial in collaborative modeling environments where multiple users may have access to the same model.

Simplified User Interaction:

Locking and unlocking should be straightforward and accessible through the UI.
Any user with access to the model should be able to lock or unlock views, elements, and folders as needed.

Benefits:

Enhances model stability and consistency by preventing unintended modifications.
Reduces the risk of accidental deletions or changes in shared models, making collaboration smoother and more reliable.

@jbsarrodie
Copy link
Member

Hi,

That's a feature Phil and I discussed some years ago. I do think it really makes sense for the use-cases you've described.

So I guess we could work on it someday, but we have lot's of things already in the backlog and Phil has been the only one to code for the past years as I have almost no free time (unfortunately), so don't expect it anytime soon.

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

No branches or pull requests

2 participants