Very serious problem, the document content read by composer does not match the actual content

I have found that sometimes it happens that after a document has been modified multiple times, when I @file in composer again, it doesn’t read the latest content, but the content of some previous version.

I’ve double-checked several times and @file the latest changes to composer, and it still thinks it’s the content of some previous version.

Such an error can have serious consequences, and I don’t think the most basic correct information can be guaranteed.

This could be caused by a bug in the refresh mechanism, but the consequences could be serious.

I hope the dev team will fix this issue soon.

Hey try this solution:

Restarting the cursor will indeed solve the problem, but if you don’t notice it, it may cause you to keep making mistakes.

1 Like