Deprecated API element remover does the wrong thing in case of deprecated base class #3025
Open
1 of 5 tasks
Labels
bug
This issue is a bug.
language/dotnet
Related to .NET bindings (C#, F#, ...)
module/pacmak
Issues affecting the `jsii-pacmak` module
p1
🐛 Bug Report
Affected Languages
TypeScript
orJavascript
Python
Java
C#
,F#
, ...)Go
What is the problem?
The deprecated API element remover generates incorrect code based on the following sources:
What happens?
SomeBaseClass
gets completely removed, but the fact thatSubclass implements ISomeInterface
does get propagated (as it should).End result is that
Subclass
does not have an implementation forsomeMethod
, and so in fact DOES NOT end up implementingISomeInterface
.This definitely fails in C#... might affect other languages too. In C# the class ends up like this:
And we then get an error that the implementation for
SomeMethod
is missing.The text was updated successfully, but these errors were encountered: