-
Notifications
You must be signed in to change notification settings - Fork 0
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
Feat/richer activation #79
base: main
Are you sure you want to change the base?
Conversation
🔍 Existing Issues For ReviewYour pull request is modifying functions with the following pre-existing issues: 📄 File: client/src/pages/Prospecting/Prospecting.js
Did you find this useful? React with a 👍 or 👎 |
✅ Deploy Preview for gleeful-cascaron-9766fa ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
@@ -31,18 +33,20 @@ import { | |||
getPaginatedProspectingActivities, | |||
} from "src/components/Api/Api"; | |||
import CustomTable from "../../components/CustomTable/CustomTable"; | |||
import ProspectingMetadataOverview from "../../components/ProspectingMetadataOverview/ProspectingMetadataOverview"; | |||
import ProspectingEffortTimeline from "../../components/ProspectingEffortTimeline/ProspectingEffortTimeline"; | |||
// import ProspectingMetadataOverview from "../../components/ProspectingMetadataOverview/ProspectingMetadataOverview"; |
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.
please remove comments
onSearch={handleSearch} | ||
/> | ||
|
||
<Box sx={{ flexGrow: 1, marginTop: 5 }}> |
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 seems like it can go in its own component
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.
Possible or advisable to put all of the new view into an AccountDetail component?
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.
Ok, got it
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, just some thoughts on componentization.
onPageChange: handlePageChange, | ||
onRowsPerPageChange: handleRowsPerPageChange, | ||
}} | ||
sortConfig={{ |
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.
@ter1203 can you include this in the CustomTable within the AccountDetail compoent? You should be able to prop drill it exactly like you're doing with pagination config, when done correctly it should result in detail table rows getting sorted when you click a column.
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.
Ok, got it.
@ter1203 Looks like the Account urls are redirecting to the app itself instead of Salesforce in the new table React.App.-.12.October.2024.mp4 |
effort-and-outcomes
…adata-grouping-api activation-detail-prospecting-metadata-grouping-api
No description provided.