Skip to content

feat: improve template version select ux - #20347

Merged
BrunoQuaresma merged 2 commits into
mainfrom
bq/improve-version-picker-ux
Oct 17, 2025
Merged

BrunoQuaresma merged 2 commits into
mainfrom
bq/improve-version-picker-ux

Conversation

@BrunoQuaresma

@BrunoQuaresma BrunoQuaresma commented Oct 16, 2025 •

Copy link
Copy Markdown
Contributor

Improvements:

  • Sort by creation date DESC
  • Show which version is active
  • Add tooltip

Demo:

Screen.Recording.2025-10-16.at.12.48.01.mov

Close coder/internal#1057

@BrunoQuaresma
BrunoQuaresma requested a review from a team October 16, 2025 16:39
@BrunoQuaresma BrunoQuaresma self-assigned this Oct 16, 2025
@BrunoQuaresma
BrunoQuaresma requested review from code-asher and removed request for a team October 16, 2025 16:39

@buenos-nachos buenos-nachos left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code looks good! Just had a few small comments

Comment thread site/src/components/Select/Select.tsx Outdated
Comment on lines +18 to +20
> & {
id?: string;
};

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know this was technically here before, but why do we need this? The Trigger type should already have an optional id prop

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💯

Comment on lines +31 to +35
.toSorted((a, b) => {
return (
new Date(b.created_at).getTime() - new Date(a.created_at).getTime()
);
}),

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we know if all of our customers can use this yet? I know toSorted broke a deployment for a customer in the past year or so because they hadn't upgraded their browser in a really long time

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It started being supported by browsers at the beginning of 2023, so I think we’re good. We don’t have a strict rule for that, but using APIs that have been available for more than two years should be safe enough.

@BrunoQuaresma
BrunoQuaresma merged commit a6461ab into main Oct 17, 2025
3 checks passed
@BrunoQuaresma
BrunoQuaresma deleted the bq/improve-version-picker-ux branch October 17, 2025 13:00
@github-actions github-actions Bot locked and limited conversation to collaborators Oct 17, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

tasks: template version picker is confusing

2 participants