use "manyCombo" field for "gender" field, restrict hairdressers to fe…

…male/male, closes #894 also partially addresses #895 and openstreetmap/iD#7427: for that iD should actually also show the "no" values allow explicitly marking the absense of certain options
openstreetmap · May 2, 2023 · 2124436 · 2124436
1 parent 43e30d2
commit 2124436
Show file tree

Hide file tree

Showing 4 changed files with 17 additions and 2 deletions.
diff --git a/data/fields/gender.json b/data/fields/gender.json
@@ -1,5 +1,5 @@
 {
-    "type": "radio",
+    "type": "manyCombo",
     "keys": [
         "male",
         "female",

diff --git a/data/fields/gender_simple.json b/data/fields/gender_simple.json
@@ -0,0 +1,13 @@
+{
+    "type": "manyCombo",
+    "keys": [
+        "female",
+        "male"
+    ],
+    "label": "{gender}",
+    "stringsCrossReference": "{gender}",
+    "options": [
+        "female",
+        "male"
+    ]
+}
diff --git a/data/presets/shop/hairdresser.json b/data/presets/shop/hairdresser.json
@@ -15,7 +15,7 @@
         "opening_hours",
         "payment_multi",
         "phone",
-        "gender"
+        "gender_simple"
     ],
     "tags": {
         "shop": "hairdresser"

diff --git a/interim/source_strings.yaml b/interim/source_strings.yaml
@@ -2160,6 +2160,8 @@ en:
         placeholder: Unknown
         # 'terms: access,female,male,unisex'
         terms: '[translate with synonyms or related terms for ''Gender'', separated by commas]'
+      gender_simple:
+        # female=*, male=*
       generator/method:
         # generator:method=*
         label: Method