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)

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 for Bug 56460 on Developer Community or GitHub if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:
Status:
CONFIRMED

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 :|