-
Notifications
You must be signed in to change notification settings - Fork 47
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 in persistentshare model and views and hook it into the target sh… #1138
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only part of the way through the review. Will try to finish tomorrow.
tom_targets/templates/tom_targets/partials/create_persistent_share.html
Outdated
Show resolved
Hide resolved
tom_targets/templates/tom_targets/target_manage_persistent_shares.html
Outdated
Show resolved
Hide resolved
tom_targets/templates/tom_targets/target_manage_persistent_shares.html
Outdated
Show resolved
Hide resolved
tom_targets/templates/tom_targets/partials/persistent_share_table.html
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some more things...
The permissions changes seem to work really well. |
It shouldn't have any effect. Anyone with permissions can see/delete any persistent shares, the user that created it is just for knowledge purposes to know who you can ask for why they did that in your collaboration. |
I get an error when I try to add a persistent share via the admin interface: |
Oops I had broken that when changing the forms before. It's fixed now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
…are page.
There are so many urls added since I added both API views with django rest framework, and template / management views for normal tom users. The template views use the DRF views to actually create/delete persistentshare instances. There is also a version of URLS that applies to all targets, vs one filtered on a specific target for both creation and management. I tried to get permissions such that only a user with target_share permissions and permissions on that specific target should be able to create a persistent share on that target.
Screencast.from.2024-12-10.06-39-48.webm