stop taginfo values from appearing also in raw editor dropdown on autoSuggestions=false, customValues=false

[matkoniecz]

See for example https://github.com/openstreetmap/id-tagging-schema/blob/main/data/fields/stop.json with

    "autoSuggestions": false,
    "customValues": false

but raw tag editor still offers and suggests extra values

I think it should not

and only values

        "options": {
            "all": "All Ways",
            "minor": "Minor Road"
        }

should be offered

see openstreetmap/id-tagging-schema#1829

[tyrasd]

Currently, the raw tag editor is by design independent from any presets/fields the feature might have. The idea is that if a user is experienced enough to use the raw tag editor, they should also know which values make sense and which don't. The taginfo-autocomplete is there only for convenience and not as an actual suggestion to use any of the values.

My first instinct was to keep this as is (as per the argument above), but maybe this should be rethought… Could you please give a few use cases where your suggestion would be better, keeping in mind that the raw tag editor is typically not used by inexperienced mappers?

[matkoniecz]

I can make fuller list, but I think that this stop= makes a good example. Other dropdown suggestions are just useless and would not be ever used.

Offering them as suggestions just makes things confusing for no reason. If field was hit with both "autoSuggestions": false, "customValues": false then it indicates that it is really a closed set of values.

User would be still able to enter freeform value, just they would not get utterly useless suggestions.

Currently, the raw tag editor is by design independent from any presets/fields the feature might have.

though I guess that risk of scope creep is real