Skip to content

fix: remove window option from open_in parameter #327

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

Merged
merged 4 commits into from
Jan 20, 2025
Merged

Conversation

defelmnq
Copy link
Contributor

The open_in parameter currently being released was first ment to contain window as one of the options - after more review it is not relevant anymore and has to be removed.

@defelmnq defelmnq requested review from johnstcn and matifali January 20, 2025 11:08
@defelmnq defelmnq self-assigned this Jan 20, 2025
@defelmnq defelmnq requested a review from mtojek January 20, 2025 11:09
Copy link
Member

@matifali matifali left a comment

Choose a reason for hiding this comment

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

LGTM. Thanks

@johnstcn I am a bit unsure about versioning for this change.
Technically, it is a breaking change. However, given that the added functionality in 2.1.0 was never released in Coder mainline or stable, it is safe to assume that no one should have been using it. And we can patch it as 2.1.1.
Thoughts?

@@ -17,18 +17,11 @@ resource "coder_agent" "dev" {
dir = "/workspace"
}

resource "coder_app" "window" {
resource "coder_app" "tab" {
Copy link
Member

Choose a reason for hiding this comment

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

The resource name is tab, so we the property coder_app.tab.open_in is available, but you're referring to coder_app.slim-window.open_in hence the issue?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes indeed , nice catch - just fixed it. 🤔

@defelmnq defelmnq requested a review from mtojek January 20, 2025 11:45
@defelmnq
Copy link
Contributor Author

Thanks @matifali @mtojek for the review and help - this one seems ready for me -

I'll need help as @matifali said above for the versioning - not sure what's the best here.

@johnstcn
Copy link
Member

LGTM. Thanks

@johnstcn I am a bit unsure about versioning for this change. Technically, it is a breaking change. However, given that the added functionality in 2.1.0 was never released in Coder mainline or stable, it is safe to assume that no one should have been using it. And we can patch it as 2.1.1. Thoughts?

Another option would be that we just make window default to slim-window and add a warning diagnostic. This would essentially have the same effect without being a 'breaking' change.

WDYT @defelmnq ?

Copy link
Member

@mtojek mtojek left a comment

Choose a reason for hiding this comment

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

I agree it is "breaking" but as long as nobody had a chance to use, maybe we should not leave "deprecation" notice? The notice will stay with us forever...

Copy link
Member

@johnstcn johnstcn left a comment

Choose a reason for hiding this comment

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

I'm OK with the current approach in any case. 👍

@defelmnq defelmnq merged commit 464d613 into main Jan 20, 2025
8 checks passed
@defelmnq defelmnq deleted the open_in_fix_options branch January 20, 2025 12:59
@github-actions github-actions bot locked and limited conversation to collaborators Jan 20, 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.

4 participants