Bug 8185 - CoreBluetooth method name spellings
Summary: CoreBluetooth method name spellings
Status: RESOLVED FIXED
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: 6.0.x
Hardware: Macintosh Mac OS
: Low enhancement
Target Milestone: Future Cycle (TBD)
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-11-02 14:56 UTC by Kirk Klobe
Modified: 2014-12-23 14:00 UTC (History)
2 users (show)

Tags:
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:
Status:
RESOLVED FIXED

Description Kirk Klobe 2012-11-02 14:56:21 UTC
A couple of suggestions on method names in CoreBluetooth:

- CBPeripheralDelegate.DiscoveredService should probably be .DiscoveredServices (iOS = peripheral:didDiscoverServices:)
- CBPeripheralDelegate.DiscoverCharacteristic should probably be .DiscoveredCharacteristics (iOS = peripheral:didDiscoverCharacteristicsForService:error:)
Comment 1 Sebastien Pouliot 2014-12-23 14:00:37 UTC
We cannot change those names without introducing a breaking change (it's more complex when typos are in delegates).

I added a comment in our binding source [1] so if we have to break compatibility (in the future) then we can consider fixing them.

[1] master 63d20d9cfec2158f45d3c1a2d97f4b304b4c59c5