-
Notifications
You must be signed in to change notification settings - Fork 231
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add group label properties #228
Conversation
Nice work! Should be ready to be merged right after 0.9 is out. |
def short_label(self): | ||
""" A short description of the group """ | ||
group_names = sorted([m.player_name for m in self.members]) | ||
group_label = group_names[0] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this how the official controllers name groups? Perhaps they use the name of the group coordinator, rather than the first in alphabetical order, i.e. group_label = self.coordinator.player_name ... etc
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lawrenceakka from what I can tell it's alphabetical; that gives a consistent name even if the coordinator isn't the first by name. It always seems to match for me, I've been using it for a few weeks.
Looks good |
It seems that there are some conflicts. Can you please rebase onto master? |
Conflicts: unittest/test_core.py
@stefankoegl rebased as requested |
Add group label properties
Making the unit tests work here required a bit of thought. The group member zgs responses had to be mocked after the group XML had been parsed, so it's done in the test code.