You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As stated in the app description, the locking mechanism provided by django-lock-tokens is not user based. That's why a lock is not tied to a user. It is supposed to also work for use cases like unauthentified resource locking.
Of course, if you use the for example django admin locking feature, this would make sense to attach a user to the lock token. We could imagine adding a nullable field (e.g. locked_by) with a foreign key to the project's user model, and set it when it is possible.
Unfortunately I don't have much time right now to develop new features for this app, but I would be more than happy to review and discuss a pull-request for this feature!
Would it be possible to register the user in the lock token? Sometimes it is unclear who locked the page.
The text was updated successfully, but these errors were encountered: