Skip to content

Keep only latest IDE in recent connections #400

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
code-asher opened this issue Apr 18, 2024 · 1 comment
Closed

Keep only latest IDE in recent connections #400

code-asher opened this issue Apr 18, 2024 · 1 comment
Assignees
@code-asher

Comments

@code-asher
Copy link
Member

code-asher commented Apr 18, 2024 •
edited
Loading

If you connect to a newer version of an IDE for a project/workspace combination, it should replace any existing recent entry.

Otherwise, you get two identical entries with no way of telling which is which. We could add the IDE version, but is there a case where you would want to connect to the older IDE?

Might not be a bad idea to add the version anyway, though.
@code-asher code-asher self-assigned this Apr 22, 2024
code-asher added a commit that referenced this issue Apr 22, 2024
@code-asher
Refactor recent connections

Unverified

This user has not yet uploaded their public signing key.
GPG key ID: 09541BBFF0C4C795
Learn about vigilant mode
Loading
Loading status checks…
5433d0a 
- Display workspace name instead of host name.
- Add deployment URL next to the workspace name.
- Add IDE product and build to the connection display (partially
  addresses #400).
- Truncate the path from the head if it is too long.
- Delete invalid recent connections.
- Delete connections with deleted workspaces (closes #396).
- Group connections by deployment URL and then workspace name.  Just a
  DX improvement, so we do not need to do janky things like
  `connections[0].name` under the assumption all the connections share
  the same name.  Could also let us create separate sections per
  deployment in the future, if we need that.
- Display status and errors under the workspace name instead of in a
  tooltip (closes #397).
- Replace config and terminal link with deployment URL
  Both of those things can be derived from the URL.  The main reason for
  this is that there might not be anything in the config when not using
  token authentication.
@code-asher
Copy link
Member Author

code-asher commented Jul 16, 2024 •
edited
Loading

There is a version column now.

And, there is also now an update mechanism by which if you launch the old connection it will try to upgrade to the latest version (if you accept the prompt) which will remove the old connection.

I think this gives a good middle ground where users can choose to have multiple versions, but it is easy to keep one up-to-date version if that is what you want.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@code-asher code-asher

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@matifali @code-asher