-
Notifications
You must be signed in to change notification settings - Fork 7
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
[TTAHUB-3095] Don't remove expired grants from the recipients dropdown when an AR is unlocked #2265
Changes from all commits
de51a81
5b4dfbf
aab5350
2c10411
8c2a5e0
fd1a662
0ef613c
440a55a
c678a4c
3a79374
7cd85f7
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -9,6 +9,7 @@ import { | |
getReports, | ||
getReportAlerts, | ||
getActivityRecipients, | ||
getActivityRecipientsForExistingReport, | ||
getGoals, | ||
reviewReport, | ||
resetToDraft, | ||
|
@@ -40,6 +41,7 @@ router.post('/', transactionWrapper(createReport)); | |
router.get('/approvers', transactionWrapper(getApprovers)); | ||
router.get('/groups', transactionWrapper(getGroups)); | ||
router.get('/activity-recipients', transactionWrapper(getActivityRecipients)); | ||
router.get('/activity-recipients/:reportId', transactionWrapper(getActivityRecipientsForExistingReport)); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. might be a useless change, but how do we feel about flipping this to be There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yeah.. I had this same thought. I'll make this change 👍 |
||
router.get('/goals', transactionWrapper(getGoals)); | ||
router.post('/goals', transactionWrapper(createGoalsForReport)); | ||
router.post('/objectives', transactionWrapper(saveOtherEntityObjectivesForReport)); | ||
|
@@ -60,5 +62,6 @@ router.put('/:activityReportId/review', checkActivityReportIdParam, transactionW | |
router.put('/:activityReportId/submit', checkActivityReportIdParam, transactionWrapper(submitReport)); | ||
router.put('/:activityReportId/unlock', checkActivityReportIdParam, transactionWrapper(unlockReport)); | ||
router.put('/:activityReportId/goals/edit', checkActivityReportIdParam, transactionWrapper(setGoalAsActivelyEdited)); | ||
router.get('/:activityReportId/activity-recipients', transactionWrapper(getActivityRecipientsForExistingReport)); | ||
|
||
export default router; |
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.
Do we need to check permissions here?
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.
I'm not actually sure. What do you think? What we're potentially exposing (to already-authenticated users) is which grant recipients were previously associated with a given AR. My initial thought is that this isn't sensitive - but maybe I"m wrong
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.
I suppose without context that info doesn't feel particularly sensitive. The only counterargument is that all the other report-related data is confined to a region. I'm ok with site-access level permissions here, personally. Although, I am not the decider.
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.
I ended up adding AR read permissions to this handler: 440a55a
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. One thing to consider is that if you are fetching the report, you no longer need to rely on the region ID being passed as a query parameter, since the report has a regionID.