chore: Removed core project

[samtrion]

Summary by CodeRabbit

• Refactor
  • Simplified solution structure by removing an internal project dependency
  • Removed unused model types to streamline the codebase

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Warning

Rate limit exceeded

@samtrion has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 11 minutes and 25 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between e6c0dfc and 87b12cb.

📒 Files selected for processing (4)

• ForgingBlazor.slnx (0 hunks)
• src/NetEvolve.ForgingBlazor/ApplicationBuilderExtensions.cs (1 hunks)
• src/NetEvolve.ForgingBlazor/Models/BlogPost.cs (1 hunks)
• src/NetEvolve.ForgingBlazor/Models/Page.cs (1 hunks)

Walkthrough

The Core project is being removed from the solution entirely. This includes deletion of the Core.csproj project file, removal of public model types (BlogPost and Page), removal of the Core project entry from the solution file, and elimination of the Core project reference from the main ForgingBlazor project.

Changes

Cohort / File(s)	Change Summary
Solution Configuration ForgingBlazor.slnx	Removed Core project entry from /src/ folder; reformatted Integration test project reference to single-line element
Core Model Deletions src/NetEvolve.ForgingBlazor.Core/Models/BlogPost.cs, Page.cs	Deleted public sealed record types BlogPost and Page that inherited from BlogPostBase and PageBase respectively
Project File Removals src/NetEvolve.ForgingBlazor.Core/NetEvolve.ForgingBlazor.Core.csproj	Removed entire Core project file including TargetFrameworks, FrameworkReference to Microsoft.AspNetCore.App, PackageReference to YamlDotNet, and ProjectReference to Extensibility
Main Project Reference Update src/NetEvolve.ForgingBlazor/NetEvolve.ForgingBlazor.csproj	Removed ProjectReference to NetEvolve.ForgingBlazor.Core.csproj while preserving Extensibility reference

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Areas requiring extra attention:

• Verify that BlogPost and Page types are not referenced elsewhere in the codebase
• Confirm that removing the Core project reference does not break the main project's build
• Check if any code in the main project or other projects depended on types from the Core namespace
• Validate that the Extensibility project contains necessary base types (BlogPostBase, PageBase) that were inherited by the deleted types

Poem

🐰 A Core once held treasures of Post and of Page,
But now they retire from this dev-rabbit's stage,
With BlogPost and Page types deleted with care,
The solution stands lighter, unburdened and fair! 🌟

Pre-merge checks

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'chore: Removed core project' accurately summarizes the main change—the complete removal of the NetEvolve.ForgingBlazor.Core project from the solution.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Knowledge base: Disabled due to Reviews -> Disable Knowledge Base setting

📥 Commits

Reviewing files that changed from the base of the PR and between d8f832b and e6c0dfc.

📒 Files selected for processing (5)

• ForgingBlazor.slnx (1 hunks)
• src/NetEvolve.ForgingBlazor.Core/Models/BlogPost.cs (0 hunks)
• src/NetEvolve.ForgingBlazor.Core/Models/Page.cs (0 hunks)
• src/NetEvolve.ForgingBlazor.Core/NetEvolve.ForgingBlazor.Core.csproj (0 hunks)
• src/NetEvolve.ForgingBlazor/NetEvolve.ForgingBlazor.csproj (0 hunks)

💤 Files with no reviewable changes (4)

• src/NetEvolve.ForgingBlazor/NetEvolve.ForgingBlazor.csproj
• src/NetEvolve.ForgingBlazor.Core/Models/BlogPost.cs
• src/NetEvolve.ForgingBlazor.Core/Models/Page.cs
• src/NetEvolve.ForgingBlazor.Core/NetEvolve.ForgingBlazor.Core.csproj

🔇 Additional comments (1)

ForgingBlazor.slnx (1)

30-30: LGTM: Formatting change only.

The reformatting of the Integration test project entry from multiline to single-line maintains the same project reference without any functional change.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84.02%. Comparing base (d8f832b) to head (87b12cb).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #25   +/-   ##
=======================================
  Coverage   84.02%   84.02%           
=======================================
  Files          16       16           
  Lines         169      169           
  Branches        9        9           
=======================================
  Hits          142      142           
  Misses         24       24           
  Partials        3        3           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.