✨ Add OSM Element Tags widget

[homersimpsons]

Implements #2453

I based my devlopments on "OSMHistoryWidget", I may not have cleaned up everything yet.

Unresolved questions:

• How to name this widget? "OSM Data", "OSM Element", "OSM Tags", "OSM Element Tags", other? (converted into comment) => OSM Element Tags
• Should I "memoize" the retrieved data? => No need
• Design improvements?
  • I tested to add borders to the table but it didn't look good.
  • I think stripped table would work (I can try to have stripped description list=
  • Maybe use a "raw" display? (just text with "tag:value\ntag2:value" (I do not think it will be easy to read)
  • How to handle long tag value? (I would say overflow ellipsis + tooltip on hover) (I did not implement this, currently ther will be a scrollbar as seen below)
  • Key on top of value? (I tested this and I do not feel like it was easier to read)

Screenshots

(With original name, not updated to "OSM Element Tags" name)

[homersimpsons]

@CollinBeczak thanks for the comments. I pushed my final update, I will let you review this. Feel free to comment anything.

[CollinBeczak]

Looks good to me! The design at the moment works and looks good.

[jake-low]

Thanks for contributing this @homersimpsons! It'll be deployed to production in our next release; I'll let you know when that happens.

[jake-low]

This is now available on maproulette.org 🙂

[homersimpsons]

This is now available on maproulette.org 🙂

Thank you for noticing me. I tried it out, but I may have made a mistake somewhere because:

1. The selected feature is not updated on page change (the list of features is correctly updated), hence when switching to the next task it will keep the old element. Do you have any idea where the issue comes from ?
2. The feature is re-fetched every time the user re-focus the windows, I should add refetchOnWindowFocus: false.

[CollinBeczak]

This is now available on maproulette.org 🙂

Thank you for noticing me. I tried it out but I may have made a mistake somewhere because it looks like the list of elements is not updated, hence when switching to the next task it will keep the old element. Do you have any idea where the issue comes from ?

The change that resolves the issue you are seeing is in this pr: #2510. I will let you know when we are planning to deploy the change when I find out.