The FullStackHero .NET 8 Starter Kit, a comprehensive tool for building cloud-ready applications, has made notable progress with the implementation of an Audit Trail feature, enhancing its auditing capabilities.
Recent issues and pull requests indicate active development focused on enhancing functionality and maintaining code quality. The open PR #1026 addresses .NET 8 compatibility issues, while closed PRs like #1017 introduce significant features such as the audit trail. Other PRs focus on routine maintenance and infrastructure improvements, such as dependency updates (#1012) and Terraform support (#1006).
Mukesh Murugan (iammukeshm)
Summary
Quantified Reports
Detailed Reports.gitignore and added appsettings.Development.json.StaticLogger.cs and Extensions.cs.Melo Y Guan (Meloyg)
Mike6x
| Timespan | Opened | Closed | Comments | Labeled | Milestones |
|---|---|---|---|---|---|
| 7 Days | 7 | 1 | 2 | 7 | 1 |
| 30 Days | 20 | 11 | 36 | 17 | 1 |
| 90 Days | 60 | 67 | 97 | 51 | 1 |
| 1 Year | 88 | 94 | 133 | 75 | 2 |
| All Time | 301 | 275 | - | - | - |
Like all software activity quantification, these numbers are imperfect but sometimes useful. Comments, Labels, and Milestones refer to those issues opened in the timespan in question.
| Developer | Avatar | Branches | PRs | Commits | Files | Changes |
|---|---|---|---|---|---|---|
| Mukesh Murugan |  |
1 | 3/3/0 | 7 | 43 | 1836 |
| Melo Y Guan |  |
1 | 1/1/0 | 1 | 2 | 44 |
| None (Mike6x) | 0 | 1/0/0 | 0 | 0 | 0 |
PRs: created by that dev and opened/merged/closed-unmerged during the period
The GitHub repository for the FullStackHero .NET 8 Starter Kit has seen a recent uptick in activity, with 26 open issues currently logged. Notably, several issues relate to urgent bugs and feature requests, indicating a mix of ongoing development and user-driven enhancements. A recurring theme among the issues is the integration of various features and troubleshooting of existing functionalities, particularly concerning multi-tenancy and API interactions.
Several issues stand out due to their complexity or urgency. For instance, Issue #903 regarding CORS errors after migrating to .NET 7.0 highlights a critical problem affecting application functionality, while Issue #1036 about Blazor Hot Reload suggests potential gaps in development tools that could hinder productivity. Additionally, the presence of multiple questions about implementing specific features indicates a need for clearer documentation or guidance.
Issue #1036: Blazor Hot Reload says No Code Changes were found
Issue #1035: How to Implement a Dropdown for Selecting a Related Entity in a Form?
Issue #1034: Is possible BaseDto Class Generate Nswag Generator
Issue #903: [BUG] CORS origin error while on subdomain
Issue #1024: Made a SQL DB.. Changed string.. rand host and I can't login.. Any idea?
Issue #1019: Added used Redis for caching in .Net 8 Aspire Starter App
Issue #1018: [Feature Req] Blazor OpenId Connect Auth with BFF in v2
Issue #1011: Blazor Debug, Breakpoints not being hit.
The current state of open issues reflects both ongoing development needs and user challenges within the FullStackHero .NET 8 Starter Kit project. Addressing these issues promptly will be crucial for maintaining user satisfaction and ensuring smooth project progression.
The analysis of the pull requests (PRs) for the FullStackHero .NET 8 Starter Kit repository reveals a vibrant and active development environment. The project has a total of 555 PRs, with 1 currently open and 554 closed. The PRs cover a wide range of updates, including feature implementations, code cleanups, dependency updates, and infrastructure improvements.
nswag-regen.ps1 script for .NET 8 compatibility. It includes updates to configuration files and generated API client code. The PR is significant as it addresses compatibility with the latest .NET version, ensuring that the starter kit remains up-to-date with current technologies.PR #1021: A cleanup PR that removes unused imports and fixes formatting issues. It's a routine maintenance task that helps keep the codebase clean and readable.
PR #1017: Introduces an audit trail feature, adding significant functionality to the application. This PR includes backend changes, API endpoint additions, and frontend updates for audit trail visibility. It's a major enhancement that improves the application's auditing capabilities.
PR #1013: Fixes configuration issues with the release drafter tool used for automating release notes generation. This PR is important for maintaining proper release management practices.
PR #1012: Updates project dependencies to their latest versions. Keeping dependencies up-to-date is crucial for security and performance improvements.
PR #1006: Adds support for Terraform modules, indicating an expansion of infrastructure as code capabilities within the project. This PR is significant for users looking to automate their deployment processes further.
PR #1005: Another update to the release drafter configuration, showing ongoing efforts to streamline release processes.
PR #999: An unmerged PR that seems to be an attempt at setting up GitHub Actions for CI/CD but was not completed or merged.
PR #990: A comprehensive update that integrates OpenTelemetry for logging, metrics, and tracing. This PR enhances observability within the application and addresses previously reported issues.
PR #973: Fixes warnings in Blazor components, contributing to better development experience and code quality.
PR #963, #957, #956, #955, #953, #952, #951, #945, #944, #943, #942, #941, #940, #939, #938, #937, and several others: These PRs cover a wide range of enhancements, bug fixes, and new features, indicating active development and continuous improvement efforts within the project.
The analysis of the pull requests reveals several key themes:
Active Development and Maintenance: The presence of both open and closed pull requests indicates ongoing development efforts. The closed pull requests show a mix of feature additions, bug fixes, and maintenance tasks, suggesting a well-rounded approach to both new development and upkeep of existing features.
Focus on Quality and Observability: Several pull requests (e.g., #1017, #990) focus on enhancing the quality of the application through features like audit trails and improved observability with OpenTelemetry. This focus on quality is crucial for production-grade applications where reliability and traceability are paramount.
Infrastructure Improvements: The inclusion of pull requests related to Terraform (#1006) suggests an emphasis on improving deployment processes through infrastructure as code practices. This aligns with modern DevOps practices where automation plays a key role in deployment efficiency and consistency.
Community Involvement: The variety of contributors (e.g., Mukesh Murugan, Mike6x) indicates active community involvement in the project. This is a positive sign as it suggests that the project is not only maintained by a core team but also benefits from contributions from external developers.
Continuous Integration/Continuous Deployment (CI/CD): Although there is an unmerged attempt at setting up GitHub Actions (#999), the presence of such efforts indicates an awareness of the importance of CI/CD in modern software development workflows. Streamlining these processes through tools like release drafter (#1013) also reflects this awareness.
In conclusion, the FullStackHero .NET 8 Starter Kit is under active development with a strong focus on enhancing its capabilities, maintaining high-quality standards, improving deployment processes, and fostering community contributions. The project's commitment to these areas is evident from the diverse range of pull requests addressing various aspects of software development lifecycle management.
Mukesh Murugan (iammukeshm)
.gitignore and added appsettings.Development.json (68 lines added).StaticLogger.cs and Extensions.cs.StaticLogger.cs and Extensions.cs.Melo Y Guan (Meloyg)
StaticLogger.cs and Extensions.cs.Mike6x