Skip to content

chore: Ship [Obsolete] markers on PostProcessResult v7-deprecated overloads#296

Open
dimension-zero wants to merge 1 commit into
fsprojects:masterfrom
dimension-zero:pr/04-v7-deprecation
Open

chore: Ship [Obsolete] markers on PostProcessResult v7-deprecated overloads#296
dimension-zero wants to merge 1 commit into
fsprojects:masterfrom
dimension-zero:pr/04-v7-deprecation

Conversation

@dimension-zero
Copy link
Copy Markdown
Contributor

Summary

PostProcessResult, PostProcessResults and TryPostProcessResult each had a // TODO for V7 [<System.Obsolete(...)>] comment that was never actioned. Convert each into a real [<System.Obsolete>] attribute pointing at the modern replacement (GetResult / GetResults / TryGetResult).

Why

The comments were debt: future maintainers had to discover they meant to deprecate these. Bodies remain unchanged so this is non-breaking — downstream consumers will see an FS0044 warning recommending the replacement, but their code still compiles.

The test suite already has #nowarn "44" at the top of Tests.fs, so the test build stays clean.

Test plan

  • dotnet build -c Release — clean (0 warnings)
  • dotnet test -c Release — 112/112 pass

`PostProcessResult`, `PostProcessResults` and `TryPostProcessResult`
each carried a `// TODO for V7 [<System.Obsolete(...)>]` comment that
was never actioned. Convert the comments into real attributes pointing
at the modern replacement names (`GetResult`, `GetResults`,
`TryGetResult`). Bodies are unchanged — consumers get a deprecation
warning, not a compile error.

The existing `#nowarn "44"` at the top of the test file already covers
the in-suite usages, so the test build stays clean.
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