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

[Suspecting caused by this] Version 1.8.0 creating a sqlite database in my project folder #207

Closed
szw0407 opened this issue Aug 24, 2023 · 2 comments
Assignees
Labels
next release This will be fixed in next release

Comments

@szw0407
Copy link

szw0407 commented Aug 24, 2023

I was using sourcery in VSCode and recently in all projects, including those witten in C++ or other languages which sourcery doesn't support, an unexpected folder appeared.

I am using VSCode on Windows 11. For example when I launch VSCode and opened a folder
D:/example/project
the folder named %example%project was automatically created, inside which is a folder named chat_history with the empty SQLite database inside.

This feature appeared to be caused by this extension as when I uninstalled the extension or downgraded it into version 1.7.0, everything was back to normal.

The new feature coming with version 1.8.0 really confused me. I was not, in fact, sure why the files are created as I didn't know this extension has a so-called Chat feature. In fact I was interested if such feature is provided, especially if it can be used in a free plan. However, I am afraid that adding such directories in my project seems improper. I recommend that a better way to store the files be considered, even putting it into .vscode is much better as it is usually in .gitignore file. However, the folder whose name is the path of my project folder is not quite proper to be added into .gitignore.

In fact I am quite glad using the old version as it works quite well. I have been using it for a long time and it really helped me write better codes.

@brendanator
Copy link
Contributor

Thanks for reporting this @szw0407. Yes, we've confirmed this is caused by us. We have a fix that will be included in the next release

@brendanator brendanator self-assigned this Aug 25, 2023
@ruancomelli ruancomelli added the next release This will be fixed in next release label Aug 28, 2023
@szw0407
Copy link
Author

szw0407 commented Sep 11, 2023

This issue seems to have been fixed in the release today. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
next release This will be fixed in next release
Projects
None yet
Development

No branches or pull requests

3 participants