On the front-end, a user cannot easily disable warnings related to a single class. Checkboxes only exist on an item level. (And I guess 99% of the users will only use the main UI)
Hence, if you disable e.g. Inconsistent tagging of construction (item 4070, class 40701) you immediately disable Finished construction and so on.
Proposal:
allow filtering the active analysers by making the checkboxes expandable to i.e. class level. So instead of e.g.:
[v] addresses
[v] combinations
[v] deprecated
... have user-expandable lists, like:
[v] ▷addresses
[v] ▼combinations
[v] missing tag
[v] suspicious tag combination
[v] {{0.key}} on a relation without {{1.key}}={{1.value}}
[v] incomplete usage of {{0.key}} on a way without {{1.key}}
[v] Use transition only as value of placement
[v] ▷deprecated
And preferably the 'Hide from map' button will only disable the specific class, not the entire item. Currently it shows Do not want to see [class title] markers? [Hide from map], but clicking it disables the entire item
Spin-off from the discussion in https://github.com/osm-fr/osmose-backend/pull/1595
On the front-end, a user cannot easily disable warnings related to a single class. Checkboxes only exist on an item level. (And I guess 99% of the users will only use the main UI) Hence, if you disable e.g.
Inconsistent tagging of construction(item 4070, class 40701) you immediately disableFinished constructionand so on.Proposal: allow filtering the active analysers by making the checkboxes expandable to i.e. class level. So instead of e.g.:
... have user-expandable lists, like:
And preferably the 'Hide from map' button will only disable the specific class, not the entire item. Currently it shows Do not want to see [class title] markers? [Hide from map], but clicking it disables the entire item