-
Notifications
You must be signed in to change notification settings - Fork 6
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
Ratings CRUD #516
Ratings CRUD #516
Conversation
Write API docs in yaml file. |
FROM organisation_members om | ||
JOIN campaigns c ON om.organisation_id = c.organisation_id | ||
JOIN applications a ON a.campaign_id = c.id | ||
JOIN application_ratings ar ON a.campaign_id = c.id |
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.
JOIN application_ratings ar ON a.campaign_id = c.id |
/// Any member of the organisation that owns the campaign is an application | ||
/// viewer, because all members are either directors or execs (TODO: might be | ||
/// changed in the future). | ||
pub async fn assert_user_is_application_reviewer_admin_given_application_id( |
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.
This whole thing might not be needed yet because if a person is an organisation member, they are also an application reviewer, so this authZ check should be covered by the function assert_user_is_organisation_member
below
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.
But we can keep it, and update the internal logic later once we add Organisation roles
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.
yoooo
No description provided.