Skip to content

Resolve "The topbar region name needs a better meaning"

MS requested to merge 1294-the-topbar-region-name-has-impact-for-the-usage into master

Closes #1294 (closed), #1072 (closed)

What does this MR do?

It forces the visible region name in the top bar to the home region, also the menu points are direct visible for the home region.

Example

Your home region as example is “Göttingen” and you join another region, but it is not your new home region. The current frontend shows the last selected region in the top bar, which is maybe a bit of confusion → because it could indicate I changed my home region.

--> https://yunity.slack.com/archives/C1T1ZM9A4/p1655310594276409?thread_ts=1655299729.468309&cid=C1T1ZM9A4

How confident are you it won't break things if deployed?

💯

Screenshots (if applicable)

CURRENT (Göttingen, is the home region) IDEA ("Stadt teil ...", is the home region)
image image

Checklist

  • added a test, or explain why one is not needed/possible...
  • no unrelated changes
  • asked someone for a code review
  • set a "for:" label to indicate who will be affected by this change
  • added to the next milestone (see https://gitlab.com/foodsharing-dev/foodsharing/-/milestones, unless it has a "for:Dev" label)
  • added an entry to CHANGELOG.md
  • added a short text that can be used in the release notes
  • Once your MR has been merged, you are responsible to create a testing issue in the Beta Testing forum: https://foodsharing.de/?page=bezirk&bid=734&sub=forum. Please change the MRs label to "state:Beta testing".
    • Consider writing a detailed description in German.
    • Describe in a few sentences, what should be tested from a user perspective.
    • Also mention different settings (e.g. different browsers, roles, ...) how this change can be tested.
    • Be aware, that also non technical people should understand.

Release notes text in German

Edited by Alex

Merge request reports