Dorian Zedler

Hmm not so sure about that. What if someone is created as a "name only" member and later registers and wants to join as a regular member, ther'd have to...

Creating name-only members is not that simple. The database has a table for users and the id of a user is the foreign key for the creditor / debtor of...

Yea, but I'll still have to change everything to use a member id instead of a user id. Since It's not a User with two subclasses, but a GroupMember with...

But I like this approach, it gives even more flexibility: - Should a user decide to leave the group, the usermember could just be turned into a dummymember - Should...

There is a `m:n` relation between user and group (many users have many groups). So you need an additional table to make this possible. This table contains memberships of users...

This would make things super complicated. And also has another problem: If dummys are users and an existing user wants to take ownership of a dummy, all occurrences of the...

> The admin of the app There is no admin... > Avoid premature optimization. This is an unfortunate approach in my opinion, as it always leads to a ton of...

> Oh. Don't you have users who have more permissions than others? Nope, I'd like to keep it simple. > And then it turns out, noone needs them in the...

You are right, that should be in a different issue, though.

Feel free to open a PR :) Do you have any experience with Typescript/React/mui? And do you have a broad concept of what you want to do?