Version: 1.2: Updated based on feedback

Author: czechboy0

Sources/swift-openapi-generator/Documentation.docc/Proposals/SOAR-0013.md

@@ -10,6 +10,7 @@ Introduce an alternative naming strategy for more idiomatic Swift identifiers, i
 - Versions:
     - v1.0 (2024-11-27): Initial version
     - v1.1 (2024-11-28): Also handle "/", "{", and "}" for better synthesized operation names
+    - v1.2 (2024-12-10): Treat "/" as a word separator and improve handling of the lowercasing of acronyms at the start of an identifier.
 - Issues:
     - [apple/swift-openapi-generator#112][issuePlugin]
     - [apple/swift-openapi-generator#107][issue1]
@@ -57,7 +58,7 @@ For clarity, we'll refer to the existing naming strategy as the "defensive" nami
 
 Part of the new strategy is adjusting the capitalization, and producing `UpperCamelCase` names for types, and `lowerCamelCase` names for members, as is common in hand-written Swift code.
 
-After attempting to produce an more idiomatic identifier, this strategy will fall back to the defensive strategy, to replace any remaining invalid symbols.
+This strategy will fall back to the defensive strategy if it encounters any invalid symbols in the identifier.
 
 The second feature introduced as part of this proposal is a way to provide a string -> string map to fully override only specific OpenAPI names and provide their exact Swift identifiers. This is the ultimate escape hatch when both naming strategies fail to provide the desired result for the adopter.
 
@@ -77,7 +78,8 @@ To get a sense for the proposed change, check out the table below that compares
 | `version 2.0` | `version_space_2_period_0` | `Version2_0` | `version2_0` |
 | `naïve café` | `naïve_space_café` | `NaïveCafé` | `naïveCafé` |
 | `__user` | `__user` | `__User` | `__user` |
-| `get/pets/{petId}` _Added in v1.1_ | `get_sol_pets_sol__lcub_petId_rcub_` | `Get_pets_petId` | `get_pets_petId` |
+| `get/pets/{petId}` _Changed in v1.2_ | `get_sol_pets_sol__lcub_petId_rcub_` | `GetPetsPetId` | `getPetsPetId` |
+| `HTTPProxy` _Added in v1.2_ | `HTTPProxy` | `HTTPProxy` | `httpProxy` |
 | `order#123` | `order_num_123` | `order_num_123` | `order_num_123` |
 
 Notice that in the last example, since the OpenAPI name contains the pound (`#`) character, the idiomatic naming strategy falls back to the defensive naming strategy. In all the other cases, however, the resulting names are more idiomatic Swift identifiers.
@@ -100,7 +102,7 @@ The idiomatic naming strategy (check out the current code [here][impl], look for
 - dashes (`-`, ASCII: `0x2d`)
 - underscores (`_`, ASCII: `0x5f`)
 - spaces (` `, ASCII: `0x20`)
-- slashes (`/`, ASCII: `0x2f`) _Added in v1.1_
+- slashes (`/`, ASCII: `0x2f`) _Added in v1.1, changed meaning in 1.2_
 - curly braces (`{` and `}`, ASCII: `0x7b` and `0x7d`) _Added in v1.1_
 
 > Note: We let [`Swift.String.isLetter`](https://developer.apple.com/documentation/swift/character/isletter) decide whether a character is a letter, which has the advantage of including letters in the non-ASCII range. Swift identifiers also support a [wide range](https://docs.swift.org/swift-book/documentation/the-swift-programming-language/lexicalstructure/#Identifiers) of alphanumeric characters.