-
Notifications
You must be signed in to change notification settings - Fork 43
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
PIMS-1623/1622: Handling project notifications and tasks #2370
Conversation
…e properties on PUT
… Fixed some logic in Task updating too. Implemented a way to update tasks when transitioning to a new status in the frontend. Revamped the documentation data card to show an immutable list of tasks organized by status.
🚀 Deployment Information The React APP Image has been built with the tag: |
…ed project correctly
Code Climate has analyzed commit 05d6671 and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 100.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 95.1%. View more on Code Climate. |
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 think we're missing the UI to display the different notes: agency, reporting, shared and private notes.
Yeah, this will just have to be another task kinda like the agency interest responses. Bummer that we sorta missed these in the initial design phase. |
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.
await projectRepo.save({ ...project, Metadata: newMetadata }); | ||
await projectRepo.save({ ...project, Metadata: newMetadata, Tasks: undefined }); | ||
//Seems this save will also try to save Tasks array if present, but if missing the ProjectId it will do weird stuff. | ||
//So we could consolidate handleProjectTasks to here if we wanted, but then it might be annoying trying to get the more specific behavior in that function. |
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.
Had this issue on a previous PR. Thought turning cascade off for that relationship would have helped, but I guess not. I think this works good enough.
if (!data || !tasks || !statuses) { | ||
return {}; | ||
} | ||
//Somewhat evil reduce where we collect information from the status and tasks lookup so that we can |
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.
Evil but clever.
import { Box, Paper, Typography } from '@mui/material'; | ||
import React from 'react'; | ||
|
||
const Forbidden = () => { |
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.
Would be good for redirections through the AuthGuard.
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.
Comitted this by accident... A leftover from when I was trying to do exactly that. We probably actually will want this eventually so I guess I won't get rid of it.
…into DisposalProjectBasicWorkflow
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.
Happy with that last change.
🎯 Summary
PIMS-1623
PIMS-1622
🔰 Checklist