Bug 33211 - PHAssetResource.Type could be PHAssetResourceType.ResourceType
Summary: PHAssetResource.Type could be PHAssetResourceType.ResourceType
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: XI 8.99 (iOS9 previews)
Hardware: PC Mac OS
: --- normal
Target Milestone: ios9/Xcode7/OSX10.11
Assignee: Bugzilla
Depends on:
Reported: 2015-08-18 21:16 UTC by Larry O'Brien
Modified: 2015-08-19 14:03 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Larry O'Brien 2015-08-18 21:16:19 UTC
Another case where "Type" will be confusing to .NET developers.
Comment 1 Sebastien Pouliot 2015-08-19 08:52:49 UTC
agreed, fixed in maccore/xcode7 4c4f0d929034bdc959c7071e3178ea5438545616
Comment 2 Miguel de Icaza [MSFT] 2015-08-19 12:31:57 UTC
I disagree to go down this path.

In general, a property named Type would never be allowed by the compiler in a context that might be a problem in the compiler.

In addition, the "Type" idiom is already widely used in Xamarin.iOS, some 68 instances exist today.
Comment 3 Sebastien Pouliot 2015-08-19 14:03:30 UTC
There's a thin and personal line between unclear and confusion, fwiw I think that:

1. Out of context (e.g. snippet, docs, online discussion, googling) it's not clear which kind of type it is;

2. .NET developers will think of System.Type first (and be wrong). Apple does not have to care as much since they use `Class` when we use `Type`;

3. There'a already many prefixed *Type properties, because several 'classes' (not to reuse 'types' ;-) already needs more than one. Anything with a single `Type` property today can find itself with `*Type` neighbors in the future;

In any case it's not major and it's true we do already have many (like typos ;-). OTOH it's something we can easily provide extra clarity in our API (at least before it's released and frozen). Feel free to revert.