Minor UI improvements #62
Merged
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
Introduce a NavBar component with section links to improve navigation within the revenue forecast page. Adjusted the div elements to include section IDs and updated scroll margin styles to enhance user experience when navigating between sections.
This commit introduces a new forecasting capability within the analytics module, facilitating the analysis of revenue data across different timeframes (one to three months ago). The primary addition is the `resolve_forecast` function, which calculates historical revenue and summarizes it per client. GraphQL schema is updated to support fetch requests for forecast data, ensuring seamless integration with existing analytics queries.
Enhanced the forecast analytics to include same-day comparisons for the consulting category. Adjusted the Python logic to calculate these new dates and their context, and updated the GraphQL schema to reflect the changes, introducing new types for consulting-specific forecasts. This increases granularity and accuracy in consulting forecasts.
Introduce a projected value to the forecast calculations based on the current progress for the month. This change involves calculating the projected total by extrapolating daily values, enhancing the overall forecast accuracy. Updated the GraphQL schema to include the new projected field in relevant sections.
Enhanced the forecasting logic by introducing an 'expected' value calculation based on the previous three months' data when available. Updated both the backend logic and the GraphQL schema to include this new 'expected' field, providing a more nuanced projection of client metrics.
Renamed the forecast query parameter from "date_of_interest" to "dateOfInterest" for consistency with camelCase naming conventions. This change improves code readability and aligns with common GraphQL schema standards.
…ling This commit simplifies the RevenueForecastPage component by removing unused state variables and functions related to date calculations, enhancing readability and performance. The GraphQL query has been updated to streamline data fetching, consolidating multiple parameters into a single dateOfInterest parameter. Additionally, the structure of the returned data has been modified to include same-day comparisons for various client categories, improving the granularity of the forecast analytics. Overall, these changes enhance the maintainability and accuracy of the revenue forecasting feature.
Introduce the 'earlyPercentage' field to the timeliness review data structure. Update the page to display the early percentage when it is greater than zero, maintaining consistency with other percentage displays.
Enable dynamic filtering of forecast data by introducing a mechanism to merge filterable fields from multiple analyses. Update schema.graphql to accept filters in the forecast query, and adjust the return type to include filterable fields. This enhancement provides more flexibility in querying forecast data and tailoring results to specific requirements.
This update introduces an optional filters parameter to the resolve_forecast function, allowing users to specify additional criteria for analyzing revenue. The filters are used across multiple date-specific computations, providing more customized and precise revenue tracking insights.
Added filter handling to the revenue forecast API and frontend to allow dynamic filtering of forecast data based on user-selected criteria. Modified backend API to accept filters and extended the frontend to provide a UI component for selecting these filters, ensuring a more tailored analytics experience.
Implemented a utility function to format numbers as currency, enhancing the presentation of financial data. Updated section headers and navigation bar to display formatted realized and expected totals. This improves clarity and readability of financial forecasts for users.
Moved forecast computation logic from the API layer to a dedicated module. This change enhances code organization and reuse by separating the computation logic from its use in the API, simplifying the forecast function in the API.
Implemented `resolve_account_manager_forecast` to compute forecasts for account managers, incorporating optional date and filters. Updated GraphQL schema and domain initialization to include forecast queries, enhancing analytical capabilities for account managers.
This commit introduces a refactor to consolidate the merging of filterable fields into a new function, improving code clarity and maintainability in the forecast model. Additionally, a new 'summary' field is added to both the model and GraphQL schema to summarize key metrics such as realized, projected, and expected values, enhancing the data insight capabilities.
Implemented a new component to display revenue progression over the last three months and the current financial performance. This enhancement includes a visual comparison of realized, expected, and projected revenues, improving the financial insights available to users. Adjusted related query and component code accordingly to support the new functionality.
Introduce a new, modular RevenueProgression component to display revenue forecasts, improving code organization and readability. Replaced the inline rendering logic in the revenue forecast page with this new component to streamline updates and maintenance.
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.