Skip to content
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

Getting rid of "Fix in chat" #451

Open
3 tasks done
skyanth opened this issue Jan 26, 2025 · 5 comments
Open
3 tasks done

Getting rid of "Fix in chat" #451

skyanth opened this issue Jan 26, 2025 · 5 comments
Labels
bug Something isn't working

Comments

@skyanth
Copy link

skyanth commented Jan 26, 2025

Checklist

Description

Since the new version, in VSCode, the refactoring popup for missing imports now has as its first option "fix in chat" where it used to be the option to add the import. There are three issues with this:

  1. I don't want to fix my issue in chat, I just want the import fix back as my first quick option
  2. Even if you choose "fix in chat" you are then sent to Sourcery's Review tab, where nothing useful is to be seen
  3. Even if you then click on chat, you see that Sourcery Chat has told you it can't add the import.

Please could you keep chat out of quick actions or give us a way to remove this option?

Debug Information

IDE Version:
1.96.4

Sourcery Version:
1.32.0

Operating system and Version:
MacOS 15.2

@skyanth skyanth added the bug Something isn't working label Jan 26, 2025
@Hellebore
Copy link
Collaborator

Hi - there's a setting to switch this off - look in the 'sourcery' section of Vs code settings, or there is also a toggle in the settings cog at the top right of the sourcery sidebar.

@skyanth
Copy link
Author

skyanth commented Jan 26, 2025 via email

@Hellebore
Copy link
Collaborator

Apologies was on my phone - are you signed up for beta releases? The 'Fix in Chat' option would have become available through the beta, since it isn't fully released yet.

Have just realised that the option to switch off will only become available with the next proper release of the extension (planned for monday or tuesday).

@Hellebore
Copy link
Collaborator

There's a change I can make today to change the precedence and put our action lower down - that'll get picked up in your beta update tomorrow.

@skyanth
Copy link
Author

skyanth commented Jan 26, 2025

Hey, thanks for addressing this so quickly. I wasn't actually aware that I was on the beta channel, the extension version doesn't give me any indication and I don't remember signing up for it (I can't even find how to do it 😂). I just have "auto update" on. Anyway, if I am on beta I guess that's on me - but I would very much appreciate the precedence change!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants