You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since v0.13, the spaceAPI officially supports the field "trigger_person", which contains the nickname of the entity which opened the space. We could draw this useful information on the widget.
The text was updated successfully, but these errors were encountered:
Well, yes and kind of no. First of all, I already use trigger_person (which is opened_by in our custom implementation) and show that info in the open/close activity. The widget itself can't show any more information, I would have to remove a currently shown part. If I wanted to show the trigger_person, I'd probably get rid of "last updated". That is handy information, but day-to-day use suggests you'll be hitting the widget anyway to get a more current status.
But there is one thing to consider designwise: The string "Last updated" and the following duration "HH:MM" is fairly fixed size, even with internationalization. Using nicknames is not. Not at all. Long nicknames will either lead to the grey textfield being larger than the widget or to truncated nicknames. I'd have to test it.
Since v0.13, the spaceAPI officially supports the field "trigger_person", which contains the nickname of the entity which opened the space. We could draw this useful information on the widget.
The text was updated successfully, but these errors were encountered: