-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[public-api] align context url with server #18292
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
Conversation
|
It maybe also would be cool to encapsulate https://github.com/gitpod-io/gitpod/blob/0bb6aaad9d4923d5510de865437f22c7f726833f/components/gitpod-protocol/src/context-url.ts#L31C28-L31C28 here instead of each client dealing with it. It is especially going to be problematic for any other runtimes but js/ts. |
|
/unhold |
| ContextUrl: input.Workspace.ContextURL, | ||
| Details: &v1.WorkspaceContext_Git_{Git: &v1.WorkspaceContext_Git{ | ||
| NormalizedContextUrl: input.Workspace.ContextURL, | ||
| NormalizedContextUrl: input.Workspace.Context.NormalizedContextURL, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does it make sense to expose the raw url in public api in the first place? I thought it's more an internal thing on server side.
I think ContextUrl should be the actual normalized context and if there's more additional metadata it should be part of Details
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We discussed this during teaming and I agree: ContextURL seems to be more of a burden than a benefit to have. The normalized one should be the default
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The question is why it was modelled like that in first place and with whom we need to discuss it then?


Description
See for context: https://gitpod.slack.com/archives/C03QM0ZHF5Z/p1689583726280819?thread_ts=1689581295.424429&cid=C03QM0ZHF5Z
Related Issue(s)
Fixes #
How to test
It should able to start a workspace from prebuild with VS Code Desktop
Documentation
Preview status
Gitpod was successfully deployed to your preview environment.
Build Options
Build
Run the build with werft instead of GHA
Run Leeway with
--dont-testPublish
Installer
Add desired feature flags to the end of the line above, space separated
Preview Environment
If enabled this will build
install/previewIf enabled this will create the environment on GCE infra
Valid options are
all,workspace,webapp,ide,jetbrains,vscode,ssh/hold