-
Notifications
You must be signed in to change notification settings - Fork 17
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
Completion suggests outdated entries #171
Comments
Did you try "Restart IDE server" (or psc-ide or whatever it is referenced as)? That should sort it without requiring a restart. Have to ask @kritzcreek what needs to happen for the old module to be discarded. |
No didn't try to restart psc-ide - thanks for the tip! Not !00% sure if I remember correctly, but I think that apart from not discarding the old module it also doesn't pick up the new one. |
The reason the old module doesn't disappear is because the externs file remains in the output directory. I don't see a good way for us to detect which files in the output directory are still valid or which are leftovers. Happy to take suggestions :D I think the filewatcher doesn't pick up new files, but that problem should be fixed once editor-mode lands. |
I think I did clean the output dir. Could it be not discarding the outdated modules for the same reason as to why it doesn't pick up new ones? Editor-mode - sounds intriguing :) What spot do I need to watch to know when it lands? |
Yeah, it doesn't because file deletion events are even less reliable than modification events. We'll have to make do with reset/reload/restart for now. |
editor-mode has now landed (maybe there's something else to do, didn't really test yet). No ideas about the general moving code question |
After moving some code around, the IDE keeps suggesting entries from the old location instead of the new one.
Also full build doesn't resolve it. However, after restarting Atom the new locations are picked up.
The text was updated successfully, but these errors were encountered: