Use Groups instead of Layers (again).

[badnames]

Basics

• The PR is rebased with current master
• I added a line to changelog.md
• Details of what I changed are in the commit messages
• References to issues, e.g. close #X, are in the commit messages and changelog
• The buildserver is happy

Checklist

• I fully described what my PR does in the documentation
• I fixed all affected documentation
• I fixed the introduction tour
• I wrote migrations in a way that they are compatible with already present data
• I fixed all affected decisions
• I added automated tests or a manual test protocol
• I added code comments, logging, and assertions as appropriate
• I translated all strings visible to the user
• I mentioned every code or binary not directly written or done by me in reuse syntax
• I created left-over issues for things that are still to be done
• Code is conforming to our Architecture
• Code is conforming to our Guidelines
• Code is consistent to our Design Decisions
• Exceptions to any guidelines are documented

First Time Checklist

• I have installed and I am using pre-commit hooks
• I am using Tailwind CSS Linting

Review

• I've tested the code
• I've read through the whole code
• I've read through the whole documentation
• I've checked conformity to guidelines
• I've checked conformity to requirements
• I've checked that the requirements are tested

[danielsteinkogler]

LGTM :D

[markus2330]

There is unfortunately a merge conflict.

[badnames]

Should be rebased now

[markus2330]

Something went wrong with the rebase.

[badnames]

Nothing went wrong.
GitHub apparently shows commits that are already in the target branch after you rebase.

https://stackoverflow.com/questions/16306012/github-pull-request-showing-commits-that-are-already-in-target-branch

[markus2330]

Diffs are now shown correctly.

This PR seems to introduce two blockers:

• visualization lines broken
• multi-select broken

Is this because of groups?

[markus2330]

please rebase