Conversation
|
@ZiyunShang Please list what functionality was broken by this PR, and we should:
|
|
Hi @ksobon - please see: your PR refactored the view classes with a new base class. This means any code that used to expect view types to inherit from I'm sorry we missed this in the PR. Maybe the fix can still be made without the new base classes - or by adding an interface as opposed to replacing the base class? - |
|
Also automating the checking of backwards compatibility is something that can be done with or ApiChange tools - it's possible but not trivial amount of work and not full proof I think. |
|
This fix is OK, but it is an API breaking change. We can file a new PR for this fix and merge it when new major, such as version 3.x, is ready. |
|
We would merge the 3dview-wrapper commits after version 3.x. Track it with link: #2290 . |
Reverts #1999
An API breaking change is made, the main 3d view classes have their base class changed. Any code that relied on the base class now breaks.
DynamoRaas functionality also now is broken because those nodes expected view3d types and now all 3d views have a base class of Abstract3dView.
FYI: @ksobon