Skip to content

Nullable problems fail the build - #185

Merged
AaronSadlerUK merged 4 commits into
dev/v17from
chore/nullable-errors
Oct 14, 2026
Merged

AaronSadlerUK merged 4 commits into
dev/v17from
chore/nullable-errors

Conversation

@AaronSadlerUK

Copy link
Copy Markdown
Member

Makes nullable problems fail the build in every project (tests included): Directory.Build.props sets Nullable to enable and WarningsAsErrors to include nullable. Null-forgiving operators (null!, default! and every other !) are gone from production and test code; nulls are handled, guarded or annotated. A source-scan test fails if any production file brings one back.

Not merged: please review.

🤖 Generated with Claude Code

AaronSadlerUK and others added 4 commits October 14, 2026 16:35
…ble; no null-forgiving operators in production or test code; source scan test; submodule pointers

Public API annotation changes (binary compatible): the LicenseService parameter of ConfigurationService, SessionService, StripeSessionService, StripeSettingsService and ConfigurationApiController is LicenseService?; CurrencyDecimals.MinorUnitDigits and ChargeableDigits take string? (they already threw for null).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…bfuscation test helper removed from the open project; neutral comments; order-independent assembly scan for linked tests

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…and no longer flags a logical not after a lambda arrow (x=>!y); test cases

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…ev/v17 merge commits (Stripe, Stripe.Forms, uSync, Stripe.uSync)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@AaronSadlerUK
AaronSadlerUK merged commit a39b7bb into dev/v17 Oct 14, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant