1. The issue and what you expected to happen

If switch users list from cards to list view, the role is displayed with ID, the same is applied to avatar as well.

It will be better if role name is displayed and image for avatar.

2. Exact steps to reproduce this issue

Go /ad

Since we also expose the Skia-bindings for a Canvas-like API I think it might be a good idea to start refactoring the API to utilise more named arguments e.g. ~x=..., ~y=....

What do you others think?

The docs are okay, but they have gotten a bit unstructured over time as we've just kept piling things on without any "refactoring". Here are some of the issues I'd like to resolve.

We welcome feedback and pull requests on any of these tasks! We need a fresh set of eyes!

General

• Clean up structure/old sections (careful not to break any links)
  • The user/developer spli

A little more explaination (in the form of an xml comment) is needed on format strings like icu_abbrev_wday_month_day_no_year, because they do require to be changed in some languages but translators often break them. We obviously can't expect everyone to understand formatter syntax ;)

/area test-and-release
/kind good-first-issue

Describe the feature

When debugging end to end tests locally, it's frequently helpful to keep resources around after the test run finishes to debug things. Currently this requires finding the call to EnsureTearDown and commenting

Is your feature request related to a problem? Please describe

We can place components inline by wrapping them with ui.inline component. But currently only start and end is supported as justify values. This blocks the user from placing the components as they please.

Describe the solution you'd like

Introduce more justify values (i.e between, around, center) to `ui.in