Bugfixes and UI improvements #65
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
- Introduced `next.config.js` to enable MDX support, allowing the use of Markdown and MDX files in the Next.js application. - Created type definitions for MDX files in `frontend/mdx.d.ts`. - Updated `package.json` to include necessary MDX dependencies: `@mdx-js/loader`, `@mdx-js/react`, and `@next/mdx`. - Implemented a new changelog page under `/admnistrative/changelog` to display changelog entries using React Markdown. - Added a hit refresh page under `/admnistrative/hit-refresh` to allow users to refresh system caches. - Removed the outdated inconsistency finder page to streamline the application. - Added a new changelog entry for the recent updates in `frontend/src/content/changelog/2024-12-10.mdx`. - Created a utility function in `frontend/src/utils/mdx.ts` to read and parse changelog entries from MDX files.
- Updated `next.config.mjs` to optimize client build by ignoring `async_hooks` for non-server environments and added `reactStrictMode: false`. - Removed the unused `App.tsx` file to streamline the application structure. - Enhanced `layout.tsx` to disable auto-refresh on tab visibility changes, improving user experience. These changes improve build performance and application responsiveness.
- Updated import path for `compute_timesheet` in `cases.py` to reflect new directory structure. - Revised title in `2024-12-10.mdx` changelog entry for improved clarity. - Enhanced changelog content to highlight the removal of page reloads during navigation, improving user experience.
- Introduced new operational summaries module, including `staleliness` query and associated GraphQL schema. - Updated `queries.py` to integrate operational summaries into the main query structure. - Enhanced `schema.graphql` to include the `staleliness` field in the Query type. - Implemented `resolve_staliness` function to process and categorize case data based on staleness criteria. - Added new GraphQL types for `Staleliness`, `StalelinessCase`, and `StalenessWorker` to support the new functionality. - Updated frontend query to fetch `slug` for cases in the operational summaries. These changes enhance the API's capabilities by providing insights into case staleness, improving data accessibility for users.
…r Links - Updated the Staleliness page to utilize the new GraphQL query structure, fetching case data directly from the `staleliness` field. - Renamed section IDs for clarity and consistency. - Removed the deprecated `categorizeCases` function, simplifying the data handling process. - Enhanced the rendering of worker names by adding links to their profiles, improving user navigation. - Updated the changelog to reflect these changes and highlight the new functionality. These updates streamline the data flow and enhance the user experience on the Staleliness page.
- Added `staleliness` field to the GraphQL `Worker` type in `schema.graphql`. - Implemented `resolve_consultant_or_engineer_staleliness` function in `consultants_engineers.py` to compute staleness based on worker data. - Updated import statements in `__init__.py` to include the new staleliness resolver. - Refactored `compute_staleliness` function in `staleliness.py` for improved logic and added a new resolver for API integration. These changes improve the API's capability to assess and return staleness metrics for workers, enhancing data accessibility and usability.
- Introduced a new `CaseStatusOverview` component to display cases categorized as "Up to Date", "Stale in One Week", "Stale", and "No Description". - Updated GraphQL queries to include `staleliness` data for consultants and engineers. - Enhanced the changelog to reflect the addition of the new feature and improvements in user navigation. - Refactored the changelog page for better layout and readability. These changes improve the user experience by providing a clear overview of case statuses for each consultant.
- Updated import paths to use the new UI components from "@/components/ui/table". - Introduced sorting functionality for both regular and pre-contracted cases, allowing users to sort by weekly approved hours, total approved hours, total actual hours, and total difference. - Redesigned the layout to include a "Pre-Contracted" section for better organization of case data. - Removed deprecated code and streamlined the rendering of case tables for improved performance and readability. - Added a new changelog entry to document these changes and improvements in user experience.
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.