- Notifications
You must be signed in to change notification settings - Fork24
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
Uh oh!
There was an error while loading.Please reload this page.
Conversation
matifali left a comment• edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
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.
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?
Uh oh!
There was an error while loading.Please reload this page.
| } | ||
| resource"coder_app""window" { | ||
| resource"coder_app""tab" { |
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 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?
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.
Yes indeed , nice catch - just fixed it. 🤔
defelmnq commentedJan 20, 2025
johnstcn commentedJan 20, 2025
Another option would be that we just make WDYT@defelmnq ? |
mtojek left a comment
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.
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...
johnstcn left a comment
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.
I'm OK with the current approach in any case. 👍
464d613 intomainUh oh!
There was an error while loading.Please reload this page.
The open_in parameter currently being released was first ment to contain
windowas one of the options - after more review it is not relevant anymore and has to be removed.