Continuation of #22. Right now a project's index status is based on whether or not some file has been indexed as opposed to all of them. This means that upon indexing canceling, an attempted index occurs on the remainder of the workspace when vscode is opened next. Additionally, the user is able to search through the partially indexed codebase
To avoid this, the metric for determining index status can be changed to whether or not project files for the project exist (indicates indexing completed). Should determine whether this is necessary, leaning towards not necessary right now due to the reconciliation progress popup (maybe make that more verbose by showing which file is being reconciled?)
Continuation of #22. Right now a project's index status is based on whether or not some file has been indexed as opposed to all of them. This means that upon indexing canceling, an attempted index occurs on the remainder of the workspace when vscode is opened next. Additionally, the user is able to search through the partially indexed codebase
To avoid this, the metric for determining index status can be changed to whether or not project files for the project exist (indicates indexing completed). Should determine whether this is necessary, leaning towards not necessary right now due to the reconciliation progress popup (maybe make that more verbose by showing which file is being reconciled?)