-
Notifications
You must be signed in to change notification settings - Fork 356
refactor: remove init flag #2313
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
base: master
Are you sure you want to change the base?
Conversation
|
Hi @CatsDeservePets, did you have any other comments about this PR, or did you want some more time to test the changes? |
I will test it some more. |
|
Sorry for taking so long. I could not find any more obvious issues and had either the same or "improved" behaviour when compared to the older code. The only thing that might be confusing is the difference in wording for some error messages. |
Extremely large refactor:
nav.dirs, which storesdirobjects separately from the directory cache, and can cause confusion. Now alldirobjects will be stored in only the directory cache, and looked up when required.nav.initflag. This was previously used to ensure thatnav.dirswas not being accessed if it was empty (i.e. before initialization).currDirandcurrFilenow load directories from the system if they are not present in the cache, so that they always return something.Hopefully this doesn't cause any crashes or other regressions. It is a very large change though so it could take some time to become stable.