While testing #636, I noticed that the members list showed only 1 member in the group after joining it, when there should be 2:

Notice it even says "2 members".
This happens in the container tab for the user who joined the group (not the container that that invited this user -- in that tab it shows both users).
Fix.
Related: #647
The correct behaviour is to only show one member - because the other member is the user who is viewing this page, who is not listed here (that is the correct behaviour).
Now, I see a different problem here - the link with the "show all x members" should not be displayed unless the group has more than 10 members. This link should also subtract 1 member (the user who is using the app).
cc @sandrina-p
This link should also subtract 1 member (the user who is using the app).
Nein. Your name should appear in both this list and the "all 2 members" list, just as it does in every other app.
@taoeffect this was not originally in the designs (meaning that @sandrina-p's implementation was correct). I will add this to my to-do list:
Fixed on the design system and dashboard mockups (Figma).
cc @sandrina-p @taoeffect
I looked into this and couldn't find the solution for it, but so far this is what I know:
state[currentGroupId].profiles length - which contains only each member hash.@taoeffect, so my question is: How it works the profiles in the store at the moment? How does a user knows what contracts should he subscribe to and where are all of these contracts saved? I looked for a bunch of files but I still struggle to understand what's going on...
@taoeffect, so my question is: How it works the profiles in the store at the moment? How does a user knows what contracts should he subscribe to and where are all of these contracts saved? I looked for a bunch of files but I still struggle to understand what's going on...
All of this is done in group.js
Well... @taoeffect that answer didn't help me much... I looked at that file but didn't understand how it works exactly. I need you to explain things in more detail.
So, this bug seems easy to fix, so maybe we could do pair programming to debug and fix it during our call tomorrow, what do you think?
So, this bug seems easy to fix, so maybe we could do pair programming to debug and fix it during our call tomorrow, what do you think?
That sounds good 馃憤
Most helpful comment
Fixed on the design system and dashboard mockups (Figma).
cc @sandrina-p @taoeffect