Bug 56460 - Spelling error in field AccurracyBestForNavigation
Summary: Spelling error in field AccurracyBestForNavigation
Status: CONFIRMED
Alias: None
Product: iOS
Classification: Xamarin
Component: General (show other bugs)
Version: XI 10.10 (d15-2)
Hardware: Macintosh Mac OS
: Lowest enhancement
Target Milestone: Future Cycle (TBD)
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2017-05-15 15:45 UTC by Al Clark [MSFT]
Modified: 2017-05-16 18:41 UTC (History)
3 users (show)

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


Attachments

Description Al Clark [MSFT] 2017-05-15 15:45:06 UTC
## Overview

Spelling error in the field AccurracyBestForNavigation including IntelliSense and Documentation.

https://developer.xamarin.com/api/field/MonoTouch.CoreLocation.CLLocation.AccurracyBestForNavigation/

This should be AccuracyBestForNavigation:

https://developer.apple.com/reference/corelocation/kcllocationaccuracybestfornavigation
Comment 1 Rolf Bjarne Kvinge [MSFT] 2017-05-16 18:28:41 UTC
This is a double-fail, we added "Accurracy" as an exception in our typo-test: https://github.com/xamarin/xamarin-macios/blob/b0b1a189882f8982a2c444fa7bfa8ca8f047496a/tests/introspection/ApiTypoTest.cs#L63
Comment 2 Sebastien Pouliot 2017-05-16 18:41:41 UTC
It's still a single fail :-) in fact it's a known issue.

When adding ApiTypoTest.cs we allowed _existing_* typos - because fixing them meant a lot of breaking changes. Even when adding alternatives (done in some cases) we still needed to make the typo test aware of existing ones.

* IOW the typo existed before the test was added (and needed to be silenced)

What's confusing is that the current list has both old typos and things we don't consider typos (like acronyms). The latter (at least the recent ones) tends to have a comment. Still we'll need to do a clean break in order to remove the formers :|

Note You need to log in before you can comment on or make changes to this bug.