Repository navigation
InitSetters: .NET 10, xUnit asserts, Tokyo coordinates fixed, new init examples - #2343
Open
vladimir-pecanac-main wants to merge 1 commit into
Conversation
…set/required/records/primary constructor examples
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
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.
Moves the InitSetters sample to net10.0 and the current xUnit, Test SDK and coverlet packages, replaces FluentAssertions with plain xUnit asserts, swaps Tokyo's latitude and longitude into the right order in Program.cs and the tests, and adds Landmark, Country, Coordinates and Airport types with four tests for the set vs init, required, record with expression and primary constructor examples the article now shows.