Skip to content

feat: show profile metadata in the picker subtitle - #107

Merged
davidborzek merged 1 commit into
mainfrom
feat/picker-metadata-fields
Aug 25, 2026
Merged

feat: show profile metadata in the picker subtitle#107
davidborzek merged 1 commit into
mainfrom
feat/picker-metadata-fields

Conversation

@davidborzek

Copy link
Copy Markdown
Owner

Profiles have carried a free-form [metadata] map for a while, but nothing
displayed it and nothing documented it. picker.info now accepts
metadata.<key>:

[metadata]
env = "staging"

[picker]
info = ["aor", "metadata.env"]

For whatever tells profiles apart that the SIP fields do not — environment,
tenant, or the extension that answers on an account whose registration username
is a device id.

The new arm replaces the _ => None catch-all, so tests pin that unknown field
names are still ignored. notes was missing from the documented field list too.

Profiles have carried a free-form `[metadata]` map for a while — the form
preserves it when editing — but nothing ever displayed it, and neither the
field nor the feature was documented. It was storage with no surface.

`picker.info` now accepts `metadata.<key>` alongside the fixed field
names:

    [metadata]
    env = "staging"

    [picker]
    info = ["aor", "metadata.env"]

This covers whatever tells profiles apart that the SIP fields do not —
which environment an account belongs to, which tenant it serves, which
extension answers on it. That last one matters when the registration
username is a device id rather than anything dialable, which is the usual
shape at a provider.

The new arm replaces the `_ => None` catch-all, so a test pins that an
unknown field name is still ignored rather than resolving to something,
and that a bare `metadata` naming no key stays empty.

`notes` was missing from the documented field list too, though it has
always worked.
@davidborzek
davidborzek merged commit 186abb6 into main Aug 25, 2026
13 checks passed
@davidborzek
davidborzek deleted the feat/picker-metadata-fields branch August 25, 2026 11:52
@github-actions github-actions Bot mentioned this pull request Aug 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant