-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make some internal/private sdk classes public and extensible #4
Comments
Any response on this? @KlausLoeffelmann can you help with similar problem please? 🙏 The code above from I can't find any information about it 🤔😳 |
Is there any hope this could happen? At least point 1? 🙏 |
Hey Kirsan, sorry for the late reply. I can't consider changing the scope for the APIs right now, but we can revisit them for the next part of the SDK we're currently working on the context of the Root Designer. |
Yea, I know that changing scope is something hard to change after release, so hope that this will be done during preview 🙏 |
internal
classes:Microsoft.DotNet.DesignTools.Client.Proxies.ProxyPropertyDescriptor
andMicrosoft.DotNet.DesignTools.Protocol.PropertyData
. It would very useful to make thempublic
, I will explain with a concrete example from chart control (I think it's all clear from comments and code). The code fromprotected override void ShowHelp()
.GetPropValue
is my extension method to get property value with reflection:Microsoft.DotNet.DesignTools.Client.Editors.CollectionEditor
we have twoprivate
classes:DefaultCollectionForm
andDefaultViewModel
. I think it would helpful to make them public with ability to extend. This should make minor modifications to the default behavior easier. I find it very costly due to minimal modification to make your own dialog like inBaseUI\DesignableCollectionEditor
example.The text was updated successfully, but these errors were encountered: