Dev to Prod #10
Merged
Dev to Prod #10
Conversation
This file contains hidden or 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
… to 9.0.10 (#5) --- updated-dependencies: - dependency-name: Microsoft.AspNetCore.Components.WebAssembly.DevServer dependency-version: 9.0.10 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…preview2 (#6) --- updated-dependencies: - dependency-name: Microsoft.Azure.Functions.Worker dependency-version: 2.50.0-preview2 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
… 2.0.2 to 2.1.0 (#7) --- updated-dependencies: - dependency-name: Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore dependency-version: 2.1.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* Upgrade to .NET 10.0 and modernize project structure Upgraded the solution to .NET 10.0, introducing a shared project for DTOs to improve code reuse. Integrated QuestPDF for server-side PDF generation and Fluent UI for a modernized Blazor WebAssembly UI. Enabled optimizations for Azure Static Web Apps, including trimming and AOT compilation. Redesigned the project reporting UI with improved error handling and loading indicators. Removed legacy code, updated dependencies (e.g., Newtonsoft.Json to 13.0.4), and streamlined service worker logic. Enhanced responsiveness, accessibility, and maintainability across the solution. Updated launch settings and assets for a polished developer and user experience. * Switch to POST for PDF generation; improve downloads Updated ProjectCompletionReportFunction to use POST, accepting the full report payload for PDF generation. Integrated QuestPDF library for robust PDF creation. Simplified error handling and adjusted logic to work with deserialized report data. Enhanced Home.razor to use POST and replaced inline PDF view with a JavaScript-based file download mechanism. Added a new `fileSave.js` utility for handling downloads. Updated index.html to include the new script. Improved user experience for PDF downloads. * Refactor documentation and improve solution clarity Updated README to reflect broader solution scope, emphasizing components, API flow, and extensibility. Added detailed documentation files (`architecture.md`, `contract.md`, `deployment.md`, `frontend.md`, `pdf.md`) covering structure, deployment, and implementation. Enhanced clarity on local development, Azure deployment, and security best practices. Highlighted the use of DTOs, QuestPDF, and Markdig for consistency and efficiency. Improved error handling, performance notes, and future extensibility options. --------- Co-authored-by: Logan Cook <[email protected]>
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR refactors the project reporting solution to use a shared DTO library, integrates FluentUI components for the Blazor front-end, adds server-side PDF generation using QuestPDF, and upgrades to .NET 10. The changes eliminate duplication between front-end and API projects while introducing a new PDF download feature that reuses existing report data.
- Consolidated DTOs into a shared project referenced by both API and Web
- Replaced custom HTML/CSS UI with Microsoft FluentUI components
- Added PDF generation endpoint that accepts pre-fetched report data to avoid re-computation
- Upgraded from .NET 9 to .NET 10 with preview packages
Reviewed Changes
Copilot reviewed 31 out of 33 changed files in this pull request and generated 7 comments.
Show a summary per file
| File | Description |
|---|---|
| Bezalu.ProjectReporting.Shared/* | New shared project containing DTO contracts used by both API and Web |
| Bezalu.ProjectReporting.Web/Bezalu.ProjectReporting.Web.csproj | Updated to .NET 10 with AOT compilation, added FluentUI packages, references shared DTOs |
| Bezalu.ProjectReporting.API/Bezalu.ProjectReporting.API.csproj | Updated to .NET 10, added QuestPDF, references shared DTOs |
| Bezalu.ProjectReporting.API/Functions/ProjectCompletionReportFunction.cs | Added PDF generation function with QuestPDF layout logic |
| Bezalu.ProjectReporting.Web/Pages/Home.razor | Replaced Bootstrap UI with FluentUI components, added PDF download functionality |
| Bezalu.ProjectReporting.Web/wwwroot/js/fileSave.js | New JavaScript helper for browser file downloads |
| docs/* | Added comprehensive documentation for architecture, configuration, contracts, deployment, front-end, and PDF generation |
| Bezalu.ProjectReporting.{API,Web}/DTOs/* | Removed duplicate DTO files in favor of shared project |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Bezalu.ProjectReporting.API/Functions/ProjectCompletionReportFunction.cs
Show resolved
Hide resolved
Bezalu.ProjectReporting.API/Functions/ProjectCompletionReportFunction.cs
Show resolved
Hide resolved
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.
This pull request introduces several important updates to the project reporting API, most notably adding PDF report generation support and refactoring DTOs into a shared project. Additionally, it updates dependencies and project configuration for .NET 10 and newer package versions.
Key changes:
Feature Additions:
GenerateProjectCompletionReportPdf) inProjectCompletionReportFunction.csto generate a project completion report as a PDF using the QuestPDF library. This endpoint accepts a full report payload and returns a downloadable PDF file.Project Structure and DTO Refactoring:
ProjectCompletionReportRequestandProjectCompletionReportResponse(and related types) from the API project, and updated code to use shared DTOs from the newBezalu.ProjectReporting.Sharedproject. [1] [2] [3]Bezalu.ProjectReporting.Sharedin the API project and created aDTOsfolder for organizational purposes.Dependency and Framework Updates:
Microsoft.Azure.Functions.Worker,Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore, andNewtonsoft.Json. Added theQuestPDFpackage for PDF generation.API Improvements:
ProjectCompletionReportFunction.csusing pattern matching for null and value checks.These changes collectively enhance the API's capabilities, modernize dependencies, and improve maintainability by centralizing DTO definitions.
References:
[1] [2] [3] [4] [5] [6] [7]