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

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

Already on GitHub?Sign in to your account

Merged
defelmnq merged 4 commits intomainfromopen_in_fix_options
Jan 20, 2025

Conversation

@defelmnq
Copy link
Contributor

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

@defelmnqdefelmnq self-assigned thisJan 20, 2025
@defelmnqdefelmnq requested a review frommtojekJanuary 20, 2025 11:09
Copy link
Member

@matifalimatifali left a comment
edited
Loading

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 in2.1.0 was never released in Codermainline orstable, it is safe to assume that no one should have been using it. And we can patch it as2.1.1.
Thoughts?

}

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 istab, so we the propertycoder_app.tab.open_in is available, but you're referring tocoder_app.slim-window.open_in hence the issue?

Copy link
ContributorAuthor

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. 🤔

@defelmnqdefelmnq requested a review frommtojekJanuary 20, 2025 11:45
@defelmnq
Copy link
ContributorAuthor

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 in2.1.0 was never released in Codermainline orstable, it is safe to assume that no one should have been using it. And we can patch it as2.1.1. Thoughts?

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

WDYT@defelmnq ?

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.

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

@johnstcnjohnstcn 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. 👍

@defelmnqdefelmnq merged commit464d613 intomainJan 20, 2025
8 checks passed
@defelmnqdefelmnq deleted the open_in_fix_options branchJanuary 20, 2025 12:59
@github-actionsgithub-actionsbot locked and limited conversation to collaboratorsJan 20, 2025
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.

Reviewers

@johnstcnjohnstcnjohnstcn approved these changes

@matifalimatifalimatifali approved these changes

@mtojekmtojekmtojek approved these changes

Assignees

@defelmnqdefelmnq

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@defelmnq@johnstcn@matifali@mtojek

[8]ページ先頭

©2009-2025 Movatter.jp