Skip to content

Add support for URI handling #37

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.

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

Closed
fioan89 opened this issue Mar 18, 2025 · 0 comments · Fixed by #35
Closed

Add support for URI handling #37

fioan89 opened this issue Mar 18, 2025 · 0 comments · Fixed by #35

Comments

@fioan89
Copy link
Collaborator

fioan89 commented Mar 18, 2025

Description
Toolbox supports URLs in the format:

jetbrains://gateway/<plugin-id>/<anything>

where:

  • <plugin-id> corresponds to the plugin’s ID as specified in the plugin's JSON configuration.
  • <anything> represents any plugin-specific components, including path, query parameters, and fragments.

Currently, the Coder Toolbox plugin needs improved handling for these URIs to ensure a seamless connection and workspace management experience.

Expected Behavior
When opening a URI, the Coder Toolbox plugin should:

  • Connect and authenticate with the specified Coder deployment.
  • Retrieve the list of available workspaces from the deployment.
  • Cross-match the retrieved workspaces with the workspace provided in the URI.
  • Navigate to the associated environment page for the matched workspace.
  • Install the specified IDE (if not already installed).
  • Launch the IDE and open the corresponding project within the remote workspace.

Additional Notes
The plugin should ensure that Toolbox has completed its initialization before executing any URI-related operations to prevent premature polling jobs.

Proper error handling and user feedback should be implemented for cases where authentication fails, the workspace is not found, or the requested IDE is unavailable.

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 a pull request may close this issue.

1 participant