-
Notifications
You must be signed in to change notification settings - Fork 1
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
Mpdx 7948 - Creating appeal details pages #984
Conversation
Bundle sizes [mpdx-react]Compared against 02e118e
|
Preview branch generated at https://MPDX-7948-creating-appeal-details-pages-2.d3dytjb8adxkk5.amplifyapp.com |
When you select or add a new contact to an appeal, it should be put in the 'Asked' category. |
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 is a huge page. Great work on everything! I've just got a couple of changes on things that don't seem to be working right.
> | ||
<Box display="flex" flexDirection="column" justifyContent="center"> | ||
<Typography component="span"> | ||
{`${pledge} ${frequency}`} |
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.
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 am asking Andrew about this as I'm not able to grab the given total without doing a separate request for each
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 Will be fixing this in a later PR
src/components/Tool/Appeal/AppealDetails/AppealLeftPanel/AppealsLeftPanel.tsx
Show resolved
Hide resolved
@@ -105,7 +105,7 @@ const Appeal = ({ | |||
className={classes.nameLink} | |||
> | |||
<NextLink | |||
href={`/accountLists/${accountListId}/tools/appeals/${id}`} | |||
href={`/accountLists/${accountListId}/tools/appeals/appeal/${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.
Do we need /appeal/ here? It seems a little repetitive.
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.
Yes, due to the flashing appeal initial page issue. To prevent the flashing initial page issue, we need to make it into a separate page.
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.
The code looks really good! Now I need to test the functionality out, but here are a few comments from just looking at the code.
src/components/Tool/Appeal/AppealDetails/AppealsMainPanel/AppealsMainPanelHeader.tsx
Outdated
Show resolved
Hide resolved
src/components/Tool/Appeal/List/AppealsListFilterPanel/AppealsListFilterPanelItem.tsx
Outdated
Show resolved
Hide resolved
src/components/Tool/Appeal/List/AppealsListFilterPanel/AppealsListFilterPanelItem.tsx
Outdated
Show resolved
Hide resolved
src/components/Tool/Appeal/List/AppealsListFilterPanel/AppealsListFilterPanelItem.tsx
Outdated
Show resolved
Hide resolved
src/components/Tool/Appeal/Flow/ContactFlowDropZone/ContactFlowDropZone.tsx
Outdated
Show resolved
Hide resolved
Now that #999 is merged, you could use the autoscroll hook I made for contact flows in appeals at some point. A follow-up PR would be fine. |
Oh also, there's a lot of new tests that use |
@canac I will do both of the edits you mention in another PR, as I don't want to screw up my commit history too much. |
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 is amazing work! I noticed a few bugs when I tried it out, but if you want to address those in future PRs, I'm good for this PR to be merged.
This get fixed in later PRs |
…components to be able to reuse them.
To fix I had to remove the initial appeal page from the appeal detail page to allow for a clean break, otherwise state was being kept and was very buggy and slow.
Fixing spelling on new appeal form Setting default settings on List view
c8577b5
to
43047d2
Compare
Description
This PR creates the Appeals Detail page structure, including the both List and Flows views. The page setup allows opening a contact drawer within the appeal details page and includes basic List and Flows pages with filtering functionality.
To make reviewing this PR easier, I have split it up into 5 different stages.
1. (Set up Appeal Detail pages)
In this step, I create the Appeal page and set it up to open 4 different types of pages. Initial appeal page, detailed list view, detailed flows view and a contact view.
2. (Clean up old files)
In this step, I remove old files and move the initial files into a folder.
3. (Appeal Details Frame )
In this step, I build out the List view, which includes the ListHeader, HeaderInfo, and some other components that are reused in the Flows view.
This step also includes the list infinite scroll and ContactRow component changes.
4. (Flows View)
In this step, I build out the Flows view, building the columns and drag and drop functionality. In this step and step 4 I try to reuse the contacts components as much as possible to prevent duplication. You will see I've edited and exported styled components & functions from the sibling contact components.
5 (Fixing issues)
In this step, I fix a few errors.
Changes
[appealId]
page to[[...appealId]]
for comprehensive path capturing.Checklist: