The deals page #94
Merged
The deals page #94
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<message> - Introduced a new "Deals" page to display active deals with potential clients, featuring a table that groups prospects and qualified leads. - Enhanced the navigation by adding a link to the new "Deals" page under the "About Us" section. - Updated the changelog to document the addition of the Deals page and its features.
- Introduced a new `DealsTable` component to encapsulate the rendering of deals, enhancing code reusability and readability. - Updated the logic to group and display both prospects and client deals separately, providing clearer insights into open deals. - Enhanced the table headers and empty state messages for better user experience. - Improved date formatting and row highlighting logic for better visual cues on deal updates. - Overall, these changes streamline the DealsPage, making it more maintainable and user-friendly.
- Changed margin classes from `mt-8 px-2` to `ml-2 mr-2` for better spacing and alignment in the DealsTable component. - This adjustment enhances the visual presentation of the deals section, contributing to a more polished user interface.
- Added a new `probability` field of type `Float` to the `ActiveDeal` GraphQL schema, allowing for more detailed deal information. - Updated the `ActiveDeal` model in Python to include an optional `probability` attribute, improving data representation and flexibility in deal management. - These changes enhance the overall functionality and data accuracy of the active deals feature in the application.
…ced deal information - Introduced a new `stageName` field in the `Deal` interface to provide additional context on the deal's current status. - Updated the GraphQL query to include `stageName`, ensuring it is fetched alongside other deal attributes. - Modified the `DealsTable` component to display the `stageName` in the table, improving the visibility of deal progression. - Adjusted the table layout to accommodate the new column, enhancing the overall user experience in the deals section.
- Introduced a new `SummaryTable` component to visualize deal summaries by stage, including counts and percentages for prospects and clients. - Enhanced the `Deal` interface by adding `stageOrderNr` to facilitate sorting of stages. - Updated the GraphQL query to fetch `stageOrderNr` alongside other deal attributes. - Improved the layout of the `DealsPage` to incorporate the new summary table, providing users with clearer insights into the deal pipeline. - These changes enhance the overall user experience by presenting a comprehensive overview of deals at different stages.
…ality - Introduced a new `SummaryTableCell` component to streamline the rendering of deal summary cells, improving code reusability and readability. - Updated the `SummaryTable` to utilize the new `SummaryTableCell`, enhancing the display of prospects, clients, and total counts with corresponding row and column percentages. - Adjusted the layout of the `DealsTable` component for better styling and alignment. - Added a new changelog entry documenting the comprehensive features of the Deals page, including detailed statistics and visual indicators for deal stages. These changes improve the user experience by providing clearer insights into deal statuses and enhancing the overall structure of the Deals page.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.