New team setup UI - #6666
Merged
Merged
New team setup UI#6666
Conversation
|
apata
reviewed
Sep 10, 2026
apata
reviewed
Sep 10, 2026
apata
reviewed
Sep 10, 2026
apata
reviewed
Sep 10, 2026
apata
approved these changes
Sep 14, 2026
ukutaht
reviewed
Sep 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes
This PR builds a new UI for the team setup page that is completely independent from TeamManagement code (which continues to work exactly the same way in team settings). The objective is to make the initial team setup UI cleaner in order to add team creation as an optional onboarding step.
The new UI is a simple form, where:
team_member_limit. Hitting the plus icon to add rows while at limit will not add any more rows and will display a "not-allowed" cursorNote: The handrolled
member-rows.jshook is quite a lot of code, but as a follow-up, I'm planning to introduce aPrima.Listboxcomponent and use it here. Somember-rows.jsshould eventually get rid of the hand-crafted keyboard navigation, focusing and blurring the dropdown, etc. We'll also be able to useListboxin the TeamManagement LiveView to make the UX feel more snappy in high-latency scenarios.Tests
Changelog
Documentation
Dark mode