-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Hide reflection additions introduced for Windows Store #111079
Conversation
Note regarding the
|
1 similar comment
Note regarding the
|
Based on #53217 (comment) (the comment after the one linked in the issue), the |
It's just a wrapper around static calls of Attribute class, CustomAttributeExtensions doesn't provide anything additional comparing to the Attribute class |
It provides the generic |
This method does just an explicit cast for the (T)Attribute.GetCustomAttribute(element, attributeType); |
Yes, but this API shape is more convenient and this is the only type that provides it. The other APIs are requested to be hidden as they're the exact same API shape as an existing API and not unique API shapes. |
@@ -12677,18 +12677,30 @@ public enum ResourceLocation | |||
ContainedInAnotherAssembly = 2, | |||
ContainedInManifestFile = 4, | |||
} | |||
[System.ComponentModel.EditorBrowsable(System.ComponentModel.EditorBrowsableState.Never)] |
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.
[System.ComponentModel.EditorBrowsable(System.ComponentModel.EditorBrowsableState.Never)] | |
[System.ComponentModel.EditorBrowsableAttribute(System.ComponentModel.EditorBrowsableState.Never)] |
ref sources should use the full type name for attributes including Attribute suffix. It is the style used by the ref sources auto-generator.
(multiple places)
Doesn't this need to goto API review for approval first? We typically treat new attributes, particularly ones like |
I think it was done as part of #53217 |
I see in #53217 (comment) that @steveharter mentioned there were some open questions remaining about scope. I'd like his review here. |
I updated #89975 to add the affected APIs and marked that issue as "api-ready-for-review". Once approved, this PR can go in. |
Yeah based on that I created #89975 to track which I just updated (see above). |
API was approved |
Fixes #89975