Closed OdyX closed 5 years ago
That's more about taxi-zebra than taxi but anyway.
I like your proposal, but this would need a change on the Zebra API side: currently the roles are returned as strings, and while I could probably split on the ❮
it would be cleaner for the API to return the roles hierarchy as tuples.
@jeanmonod what do you think about adding this format in the API?
@sephii Why not. But this is also going to impact all dropdown on Zebra. So I would to have Tom view on this one. I created a ZBR ticket for that https://jira.liip.ch/browse/ZBR-2668
@jeanmonod if we make the API return each role as a tuple (eg. ('GCC', 'Internal IT', 'Rep Link')
), the representation would then be done by the API consumer (eg. taxi) so that would be independent from Zebra.
I am totally for the role grouping, but I think reverting the representation doesn't really bring value. Why not first just only group roles to start with? :)
Fixed in taxi-zebra 1.4.6.
It would be easier if roles were somehow sorted; clustered by circle (sorted by depth, then alphabetically), then special roles (Lead Link, Rep Link, Secretary, Facilitator) first, then alphabetically.
I'd also revert the Circles-to-Roles hierarchy order.
I have the following prompt currently:
What about displaying these same roles as: