"fix using copilot" no longer context aware?

[rpuls]

Select Topic Area

Question

Body

My project is filled with tens of thousand of require statements, and not a single import. My setup does not support import. Yet for some reason, copilot have started suggesting to fix 'not defined' with an import statement. This was not the case a few weeks (maybe a month) ago, it used to be able to follow the code pattern of my project. This new behavior is consisten, it suggest using import every single time.

I had similar experience with /tests that it would write unit tests using an assertion syntaxt that doesn't exist anywhere in my repo, despite haivng thousands unit tests all using same assertion library and same function calls. But this issue seems to have been fixed, because today it successfully generated two unit test with the syntaxt used across the repository.