You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes it only makes sense to display a field if certain tags are present on the feature. For example, the Payment Types field would be useful on presets such as Parking Lot, Telephone, or Toilets, but only when fee=yes. Another use would be in #5580, where the field for diet:vegetarian would be redundant if diet:vegan=yes.
I propose finding a generalized solution where conditions can be defined in JSON and not in code.
Sometimes it only makes sense to display a field if certain tags are present on the feature. For example, the Payment Types field would be useful on presets such as Parking Lot, Telephone, or Toilets, but only when
fee=yes
. Another use would be in #5580, where the field fordiet:vegetarian
would be redundant ifdiet:vegan=yes
.I propose finding a generalized solution where conditions can be defined in JSON and not in code.
Related: #4871
The text was updated successfully, but these errors were encountered: