Skip to content

Investigate API typos found by introspection TypoTest #25397

@rolfbjarne

Description

@rolfbjarne

The introspection TypoTest spell-checks our API names and maintains an allowed-word list. A recent cleanup of this test (PR #25393) identified a number of words that appear to be genuine typos in Apple's APIs (or our bindings of them).

Two analysis files have been created with the full list of typos and their source references:

Each typo entry includes a permalink to the source code and the actual code line.

Task

Go through the list of typos in both files and decide for each one:

  1. Real typo — fix it: Add a properly spelled API alongside the misspelled one, and obsolete the old one. This applies to typos in our bindings (e.g. missing camelCase splits like AdjustmentforAdjustmentFor, or misspellings like AchivementsAchievements).

  2. Not a typo / Apple's spelling: If the misspelling originates from Apple's API and we must match it exactly, document why the word is in the allowed list (e.g. Referer is the historic HTTP spelling from RFC 2616). These should not be "fixed" but could benefit from better documentation.

Examples from the lists

Word Issue Category
Achivements achievements (missing e) Our binding — fixable
Adjustmentfor AdjustmentFor (missing camelCase) Our binding — fixable
Referer referrer (RFC 2616 spelling) Apple/HTTP convention — document
Tesselation tessellation (single l) Apple's spelling — document
Cancellable cancelable (British variant) Acceptable variant — not a typo

Metadata

Metadata

Assignees

No one assigned

    Labels

    testsAnything related to tests

    Type

    No fields configured for Task.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions