Skip to content

Conversation

@gmottajr
Copy link
Contributor

Migration to .NET 8: .csproj files are being updated.

  • \C-Sharp\Algorithms\Algorithms.csproj
  • \C-Sharp\Algorithms.Tests\Algorithms.Tests.csproj
  • \C-Sharp\DataStructures\DataStructures.csproj
  • \C-Sharp\DataStructures.Tests\DataStructures.Tests.csproj
  • \C-Sharp\Utilities\Utilities.csproj
  • \C-Sharp\Utilities.Tests\Utilities.Tests.csproj

Please let me know whether or not it would be necessary to create new unit tests for this change.

Motivation and Context

Github issue #425: Proposed to migrate to .NET 8 to use the latest features of .NET ecosystem. It was requested to perform the changes in a few PRs to make them smaller and easier to review. This is the one only meant to update .NET version.

  • I have performed a self-review of my code
  • My code follows the style guidelines of this project
  • All existing unit tests have been executed, and all have passed successfully.
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Comments in areas I changed are up to date
  • I have added comments to hard-to-understand areas of my code
  • I have made corresponding changes to the README.md
Migrating to .NET 8 changes the way the project is built or introduces new requirements (like a specific version of the .NET SDK), it's important to update the README to reflect these changes. New Features or Limitations: The migration introduces new features (like utilizing new C# language features) or has specific limitations (such as compatibility issues with certain environments), these should be documented. Testing and Usage Instructions: The migration impacts how tests are run or how the project should be used, updating the README is necessary to guide other contributors or users.
@gmottajr gmottajr requested a review from siriak as a code owner December 27, 2023 03:32
@codecov
Copy link

codecov bot commented Dec 27, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (915e364) 94.50% compared to head (92cecc7) 94.46%.

Additional details and impacted files
@@ Coverage Diff @@ ## master #426 +/- ## ========================================== - Coverage 94.50% 94.46% -0.05%  ========================================== Files 234 234 Lines 9843 9843 Branches 1451 1455 +4 ========================================== - Hits 9302 9298 -4  - Misses 381 384 +3  - Partials 160 161 +1 

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

@siriak
Copy link
Member

siriak commented Dec 27, 2023

Please also update .NET version in ci.yml

@gmottajr
Copy link
Contributor Author

Sure, done!

@siriak
Copy link
Member

siriak commented Dec 28, 2023

Please fix Codacy issues. Codecov is fine, I can merge with that.

@gmottajr
Copy link
Contributor Author

I'm not getting any issue. Perhaps I'm going to ne you showing me what you see.
Nothing shows up to be fixed here so far.
image

@siriak
Copy link
Member

siriak commented Dec 29, 2023

They are here. You can click on Details to see details.
image

…ggestions from Codacy Static Code Analysis, particularly about the unordered list marker style in the README.md, suggesting a change to the * marker style.
@gmottajr
Copy link
Contributor Author

Gotcha!
Changed as per request.
Thank you for the clarification.

Copy link
Member

@siriak siriak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, thanks!

@siriak siriak merged commit 821f492 into TheAlgorithms:master Dec 29, 2023
@gmottajr
Copy link
Contributor Author

You are welcome!
I'm going to jump to the next group of changes, be right back soon. Thank you very much!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants