style: apply repo-wide code formatting#18
Merged
Merged
Conversation
Apply the configured ReSharper/formatter layout across the solution (attribute placement, member layout, whitespace). One semantic side-effect was corrected: the cleanup turned a test helper property get-only, breaking PropertyPathTests.Setter_Property_WritesValue (the property is written via an expression-tree setter the analyzer can't see) — restored its setter. No production property lost a setter (verified) and the full suite is green.
|
|
||
| using var wrong = new EntryCipher(RandomNumberGenerator.GetBytes(32), 65536); | ||
| encrypted.Position = 0; | ||
| await Assert.ThrowsAsync<AuthenticationTagMismatchException>(() => wrong.DecryptAsync(encrypted, new MemoryStream()) | ||
| await Assert.ThrowsAsync<AuthenticationTagMismatchException>( | ||
| () => wrong.DecryptAsync(encrypted, new MemoryStream()) |
| new MemoryStream(Encoding.UTF8.GetBytes(secretArmored)) | ||
| ); | ||
| var ring = new PgpSecretKeyRingBundle(input).GetKeyRings().Cast<PgpSecretKeyRing>().First(); | ||
| using var input = PgpUtilities.GetDecoderStream(new MemoryStream(Encoding.UTF8.GetBytes(secretArmored))); |
| { | ||
| [ObservableProperty] | ||
| private string _title = "SquidStd.Tui — Counter"; | ||
| [ObservableProperty] private string _title = "SquidStd.Tui — Counter"; |
| catch (OperationCanceledException) | ||
| { | ||
| } | ||
| catch (OperationCanceledException) { } |
| ? logDirectory | ||
| : Path.Combine(Options.RootDirectory, logDirectory); | ||
| ? logDirectory | ||
| : Path.Combine(Options.RootDirectory, logDirectory); |
| catch (OperationCanceledException) when (cancellationToken.IsCancellationRequested) | ||
| { | ||
| } | ||
| catch (OperationCanceledException) when (cancellationToken.IsCancellationRequested) { } |
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.
Summary
Repo-wide application of the configured formatter/ReSharper layout (attribute placement on their own line, member layout, whitespace) across 621 files. Whitespace/layout only — no production behaviour change.
Safety check
A format sweep can introduce semantic changes via "make get-only" cleanups. I gated this:
PropertyPathTests.Setter_Property_WritesValue(the property is assigned through an expression-tree setter the analyzer can't see). Restored its setter.src/.Test plan