Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

feat: add OpenIn option to coder_app#15743

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
defelmnq merged 29 commits intomainfromcoder_app-open_in
Jan 3, 2025
Merged

feat: add OpenIn option to coder_app#15743

defelmnq merged 29 commits intomainfromcoder_app-open_in
Jan 3, 2025

Conversation

defelmnq
Copy link
Contributor

@defelmnqdefelmnq commentedDec 4, 2024
edited
Loading

This PR is the coder/coder part ofthe open_in parameter issue aiming to add a new optional parameter to choose how to open modules.

This PR is heavily linkedto this PR.

ℹ️ For now, some integrations tests can not be pushed as it requires a release on the terraform-provider repo.

@defelmnqdefelmnq self-assigned thisDec 4, 2024
@github-actionsgithub-actionsbot added the staleThis issue is like stale bread. labelDec 12, 2024
@johnstcnjohnstcn reopened thisDec 16, 2024
@github-actionsgithub-actionsbot removed the staleThis issue is like stale bread. labelDec 17, 2024
@defelmnqdefelmnq changed the titleAdd OpenIn option to coder_appfeat: add OpenIn option to coder_appDec 17, 2024
@defelmnqdefelmnq marked this pull request as ready for reviewDecember 18, 2024 14:41
@defelmnqdefelmnq requested review frommtojek and removed request forspikecurtisDecember 18, 2024 14:41
Copy link
Member

@mtojekmtojek left a comment

Choose a reason for hiding this comment

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

Nice work! LGTM 👍 ... but please wait for double-check from@johnstcn

You may want to mention the next steps like:

  • adjust Coder UI
  • update the dependency on terraform-provider-coder
  • etc.

johnstcn
johnstcn previously approved these changesDec 19, 2024
Copy link
Member

@johnstcnjohnstcn left a comment

Choose a reason for hiding this comment

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

LGTM, only suggestion I have is to defineopen_in as an enum instead, similar to how some other fields of the table are defined.

@defelmnq
Copy link
ContributorAuthor

defelmnq commentedDec 23, 2024
edited
Loading

@mtojek@johnstcn I modified a lot of the code since your last review to add :

  • Enum on the database
  • Enum in proto files in the protosdk

Can I ask you for another stamp ? 🙏

CI is ok but just waiting for storybook review (which are false positive, nothing changed.)

@mtojek
Copy link
Member

I reviewed Storybook images and they seem to be correct 👍

Copy link
Member

Choose a reason for hiding this comment

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

When adding a new field to this protobuf, you will need to incrementprovisionerd.proto.CurrentMinor.

Copy link
Member

Choose a reason for hiding this comment

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

TIL - is it documented somewhere? I believe there is no linting rule.

Copy link
Member

Choose a reason for hiding this comment

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

I'm second-guessing myself now -- we definitely need to increment minor version when adding a new RPC method.

mtojek reacted with thumbs up emoji
Copy link
Member

Choose a reason for hiding this comment

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

Yep, no need to increment here. Sorry for the confusion!

Copy link
Contributor

Choose a reason for hiding this comment

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

Wedo need to increment the minor version:

https://www.notion.so/coderhq/API-Changes-Back-Compatibility-36e779e691e140d4a3dcb78700c6d0bf?pvs=4#21fc01f1d65847d1a2cff6a2558def76

This is a new feature, not a bug fix, so it gets a minor version increment.

Copy link
Member

Choose a reason for hiding this comment

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

Apologies for the confusion! I opened a separate PR to add some guidelines so we don't get confused about this in future:#16009

@@ -2559,6 +2559,7 @@ export interface WorkspaceApp {
readonly healthcheck: Healthcheck;
readonly health: WorkspaceAppHealth;
readonly hidden: boolean;
readonly open_in: string;
Copy link
Member

Choose a reason for hiding this comment

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

Defining this as a typed const in the Go code will mean this becomes a proper type in the generated TypeScript code.

Copy link
Member

Choose a reason for hiding this comment

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

I think we'll also need to create a newConnectRPC24 method incodersdk/agentsdk to handle this new field, which defines an API version of major = 2 and minor = 4 adding this new field. Correct if I'm wrong@spikecurtis ?

Copy link
Member

Choose a reason for hiding this comment

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

Looking through#15508 again, it looks like I'm making much ado about nothing. We only need to bump the version when we modify the method interface, but adding a struct field to a proto shouldn't cause any issues. Please disregard the above comment.

@johnstcnjohnstcn dismissed theirstale reviewDecember 24, 2024 09:33

bump api versions

Copy link
Member

@johnstcnjohnstcn left a comment

Choose a reason for hiding this comment

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

requesting changes to clarify changes to api versions

Copy link
Member

@johnstcnjohnstcn left a comment

Choose a reason for hiding this comment

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

Clarified api version changes. I think we still should define the externally-facingcodersdk field as a typed const, but I think that's the last piece. Re-approving to un-block.

Copy link
Member

Choose a reason for hiding this comment

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

Looking through#15508 again, it looks like I'm making much ado about nothing. We only need to bump the version when we modify the method interface, but adding a struct field to a proto shouldn't cause any issues. Please disregard the above comment.

Copy link
Member

Choose a reason for hiding this comment

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

Yep, no need to increment here. Sorry for the confusion!

@github-actionsgithub-actionsbot added the staleThis issue is like stale bread. labelJan 1, 2025
Copy link
Contributor

Choose a reason for hiding this comment

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

Wedo need to increment the minor version:

https://www.notion.so/coderhq/API-Changes-Back-Compatibility-36e779e691e140d4a3dcb78700c6d0bf?pvs=4#21fc01f1d65847d1a2cff6a2558def76

This is a new feature, not a bug fix, so it gets a minor version increment.

@@ -100,7 +100,7 @@ require (
github.com/coder/quartz v0.1.2
github.com/coder/retry v1.5.1
github.com/coder/serpent v0.10.0
github.com/coder/terraform-provider-coder v1.0.2
github.com/coder/terraform-provider-coder v1.0.4
Copy link
Member

Choose a reason for hiding this comment

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

Shouldn't this go tov2.1.0?

Copy link
Member

Choose a reason for hiding this comment

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

@defelmnq I am certainly not familiar with the code base as you but why we are still on version 1.0.4 of provider here?

@github-actionsgithub-actionsbot removed the staleThis issue is like stale bread. labelJan 3, 2025
Copy link
ContributorAuthor

@defelmnqdefelmnq left a comment

Choose a reason for hiding this comment

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

All comments should be fixed and the PR ready to merge - I tested in dogfood and everything's working.

cc@spikecurtis for the version bump.

Copy link
Contributor

@spikecurtisspikecurtis left a comment

Choose a reason for hiding this comment

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

One comment inline, but I don't need to review again.

@defelmnqdefelmnq merged commit08463c2 intomainJan 3, 2025
33 of 34 checks passed
@defelmnqdefelmnq deleted the coder_app-open_in branchJanuary 3, 2025 10:27
@github-actionsgithub-actionsbot locked and limited conversation to collaboratorsJan 3, 2025
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.
Reviewers

@johnstcnjohnstcnjohnstcn approved these changes

@matifalimatifalimatifali left review comments

@mtojekmtojekmtojek approved these changes

@spikecurtisspikecurtisspikecurtis approved these changes

Assignees

@defelmnqdefelmnq

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

5 participants
@defelmnq@mtojek@johnstcn@spikecurtis@matifali

[8]ページ先頭

©2009-2025 Movatter.jp