Always allow going back to last step in menus about id HOT 6 OPEN

Hi @jidanni,
I came across this repository and am intrigued by the issue at hand. Given my experience with Javascript and other front-end frameworks, I believe I can contribute effectively to its resolution. Would you mind assigning this issue to me? Thanks!

from id.

This is the standard behaviour for sub-presets in id-tagging-schema. Here, 'trunk', etc. are not a (sub)-type of 'alley'. Note there is also presets such as 'Information' (tourism=information) with type like board, with its own sub-type like history. Adding back(other case: duplicating) 'type' field introduces extra work and only causes confusion and clutter for the user.

In iD (and Rapid), you have at least

• Undo button, as previously mentioned by both yourself and Quincy in #8249 (top right) and hotkey (Ctrl + Z)
• Feature Type button still, which should display most recently used preset(s), like so
  (notably it sometimes doesn't, since either the code's logic doesn't understand it, or the object type was intentionally made unsearchable as it is unspecific or deprecated)

• Raw tags when we scroll down, we can choose to modify it manually or (switch) to display options (and auto-fill), like so

(we could also choose to manually delete this sub-tag, which would yield the same result as hitting the undo button)

• Refresh the editor and simply start over if all else fails.

• (sidenote: in iD 'v3' concept there are preset buttons/keys, so if you map these objects often you can switch easily)

Note: User can (and should) also still verify they have the right preset regardless of 'type' field disappearing by clicking 'i' info icon next to feature type.

Also, in some cases, it may be faster to search for the preset directly (presented with multiple options) than to search generic term, select generic preset and finally selecting type. Individual presets can have unique terms/synonyms.

Furthermore, sometimes it is more likely users will make mistake confusing preset with completely different object type. There type menu will not help the user. (And, in this case it can be beneficial to have user check documentation.)

(sidenote: fields not tied to presets can always be modified, or will understandably only add additional field(s), i.e. wikipedia adds wikidata); though adding wikidata will block name modification (usually vandalism/accident).

from id.

@danieldegroot2
I am seeking clarification on your recent communication. Does it imply that there is no need for further investigation? Alternatively, if there are additional tasks or areas requiring attention, I am eager to contribute.

from id.

@DependerKumarSoni I would suggest reading CONTRIBUTING.md and checking out also list of examples of other projects and Google Summer of Code ideas (announcement for 2024). Usually there is issues labeled good first issue (for iD there is currently only 'don't display deprecated tags' issue without existing PR).

from id.

@DependerKumarSoni You're assigned!

Wait, I forgot. I'm not in charge here.

from id.

All I know is I thought my request might make things in iD a little more intuitive. However if "fixing it" would instead make iD worse, then OK, close the bug.

from id.