@Astul-Betizagasti noted that currently they are obsoleting the old controls, so I think it's fine to do the same here for now until we discuss API surface rules.

@mjkkirschner, related about what you were saying about WPF Controls (not sure if you are just talking about Properties in the ViewModel or controls in the XAML file), some days ago I created a new pull request for enabling the Geometry Scaling and Render Precision features in the Preferences panel, so I deleted the old code related to the Geometry Scaling functionality (xaml, code behind, events, commands, methods .....), is that ok? or should I marked as Obsolete?
This is the pull request:
#11657

Thanks
cc: @Astul-Betizagasti

@RobertGlobant20 - I'm not sure - I think the safest thing to do for now is to obsolete anything public, add a TODO and we should discuss with @QilongTang how to approach it.

If we are going to start treating public methods and classes in DynamoCoreWPF as excluded from our API we should message this out, and at the minimum it must be documented it in the github readme or dev docs.
AFAIK we do treat some extensions like this already - but it's not consistent or documented well.

for this PR - that was what I was going to do -

1. obsolete the unused controls for now.
2. file a task to remove them at 3.x time in any case.
3. discuss with teams if we want to create a new policy and how we should message it.

Hey @mjkkirschner What we used to do was that:

Currently, we are treating DynamoView out of API scope, which means we can move/delete XML wpf controls as we want. For any public properties exposed under DynamoViewModel, we were only obsoleting them.

If you have any preference, feel free to update here or on slack conversation: https://autodesk.slack.com/archives/C01C2AGPSG2/p1620055650102300

@QilongTang okay - will proceed same as Morpheus team, filed a task for the messaging.