Repository navigation
feat(ui-ng): add access picker component - #671
Conversation
![ferrfleet-interne[bot]](https://avatars.githubusercontent.com/in/5311663?s=60&v=4){kind=small}
There was a problem hiding this comment.
Both earlier findings are fixed in 5a729db: pickedScopes is now a linkedSignal, and stale org ids are filtered out. No new issues.
There was a problem hiding this comment.
31893eb only changes the stories: output now goes through a report host callback bound to the fn() spy. Looks right, and I found no new issues.
There was a problem hiding this comment.
124fe6e only touches the stories: expectLast and the aria-pressed checks now sit in waitFor, so they no longer race the effect that emits. The expected values match what the model functions produce. Nothing new found.
There was a problem hiding this comment.
4f91e8e only touches the stories: the fn() spy is gone, report writes the last emission to a <pre data-testid="selection">, and expectLast checks that text inside waitFor. The expected values still match what the model produces. Nothing new found.
## [1.45.0] - 2026-10-20 ### Features - feat(ui-ng): add access picker component (#671)
1 participant
Adds
flr-access-picker, ported from the consent screen in FerrLabs-Cloud (feat/token-org-allowlist) so site settings pages can reuse it.Inputs: orgs, catalogue, presets, initialScopes, labels (EN/FR constants). Output: selectionChange emits { orgIds: string[] | null, scopes: string[] } or null when invalid. Styled with ui-foundation tokens.
Tests are Storybook play functions (Forms/Access picker). The test-runner could not run in my environment (no browser libs), so they are unverified in CI-less form; the pure selection logic was checked in node and the package and showcase build.