-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Porting System.Windows.Forms.Design.ListControlStringCollectionEditor #2078
Porting System.Windows.Forms.Design.ListControlStringCollectionEditor #2078
Conversation
Needs review before testing. |
Its probably not enough to just add the editor, it must be linked up with the TypeDescriptor. We've had a whole bunch of other editor porting issues (e.g. #1119, #1120, #1121) due to the editors not being linked up correctly. If possible we should do it correctly here in the first place instead of waiting for reports of it not working correctly. |
@weltkante, thank you, I'll check it. |
This comment has been minimized.
This comment has been minimized.
Codecov Report
@@ Coverage Diff @@
## release/3.1 #2078 +/- ##
=====================================================
+ Coverage 26.50723% 26.51319% +0.00596%
=====================================================
Files 806 806
Lines 268108 268093 -15
Branches 38070 38069 -1
=====================================================
+ Hits 71068 71080 +12
+ Misses 191957 191933 -24
+ Partials 5083 5080 -3
|
@vladimir-krestov sorry, I was overly cautious, this will probably just work, |
@weltkante , anyway, thank you for your information. |
...ws.Forms.Design.Editors/src/System/Windows/Forms/Design/ListControlStringCollectionEditor.cs
Outdated
Show resolved
Hide resolved
...ws.Forms.Design.Editors/src/System/Windows/Forms/Design/ListControlStringCollectionEditor.cs
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, a few nits
Just to clarify, because the editor was originally defined in System.Design.dll we need to set type forwarding. We can resolve nits later. |
📢 Please note due to a limited timeframe and the scope of work we are going to expediate all UI type editors ports into 3.1 and are going to ignore all stylistic review points. |
@vladimir-krestov please rebase to resolve the MC |
f9064da
to
7212336
Compare
Rebased to the latest release branch. |
approved from my end. Please add the servicing: consider label after testing completes. |
972f7fb
to
e5ee0d0
Compare
Rebased to |
6b1ac54
to
c66cfff
Compare
c66cfff
to
9833f86
Compare
|
||
using System.Runtime.CompilerServices; | ||
|
||
[assembly: TypeForwardedTo(typeof(System.Windows.Forms.Design.ListControlStringCollectionEditor))] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we still need StringCollectionEditor
and ArrayEditor
...
Whilst we do not support nor cant be expected to support customers who reference our internals, in some scenarios like `UITypeEditor`s and `TypeConverter`s may still be used by consumers to enhance their runtime experience. E.g. dotnet#2078 (comment) Type forward `DataMemberFieldConverter` to avoid breaking existing customers. Relates to dotnet#1545
Whilst we do not support nor cant be expected to support customers who reference our internals, in some scenarios like `UITypeEditor`s and `TypeConverter`s may still be used by consumers to enhance their runtime experience. E.g. #2078 (comment) Type forward `DataMemberFieldConverter` to avoid breaking existing customers. Relates to #1545
Whilst we do not support nor cant be expected to support customers who reference our internals, in some scenarios like `UITypeEditor`s and `TypeConverter`s may still be used by consumers to enhance their runtime experience. E.g. #2078 (comment) Type forward `DataMemberFieldConverter` to avoid breaking existing customers. Relates to #1545
Whilst we do not support nor cant be expected to support customers who reference our internals, in some scenarios like `UITypeEditor`s and `TypeConverter`s may still be used by consumers to enhance their runtime experience. E.g. #2078 (comment) Type forward `DataMemberFieldConverter` to avoid breaking existing customers. Relates to #1545
Fixes #1271
Related issue: #1115
Have you experienced this same bug with .NET Framework?: No
Proposed changes
Customer Impact
Regression?
Risk
Screenshots
Before
After
Test methodology
Test environment(s)
Microsoft Reviewers: Open in CodeFlow