Skip to content

Obsolete the never-implemented type-handler pair as a warning, not an error - #209

Merged
mgravell merged 1 commit into
mainfrom
soften-typehandler-obsolete
Aug 25, 2026
Merged

Obsolete the never-implemented type-handler pair as a warning, not an error#209
mgravell merged 1 commit into
mainfrom
soften-typehandler-obsolete

Conversation

@mgravell

Copy link
Copy Markdown
Member

TypeHandlerAttribute<TValue, THandler> and TypeHandler<T> were obsoleted as errors in #208. Softening to warnings for the first release that carries the replacement.

Nothing depends on their behaviour — they have always been no-ops — but code that names them compiles today, and per the discussion on #173 people did write them. An error turns an upgrade into a build break; a warning still names the replacement ([TypeHandler(typeof(V), typeof(H))] + IDbValueHandler<T>) and gives people a release to move before it hardens.

One-word change, plus the message text. Suite green (366 net8.0), solution builds clean.

… error

Both types have always been no-ops, so nothing depends on their behaviour - but
code that names them does compile today, and an error breaks that build on
upgrade. A warning still says what to use instead, and gives people a release
to move at their own pace before it hardens.
@mgravell
mgravell merged commit 07795e3 into main Aug 25, 2026
2 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