Skip to content
This repository has been archived by the owner on Dec 14, 2021. It is now read-only.

don't force fully reindexing on settings change #493

Closed
TTimo opened this issue Oct 24, 2017 · 4 comments
Closed

don't force fully reindexing on settings change #493

TTimo opened this issue Oct 24, 2017 · 4 comments
Assignees
Labels

Comments

@TTimo
Copy link
Contributor

TTimo commented Oct 24, 2017

Feature request..

I added an include path to fix a handful of files that couldn't find a header. I don't want to be forced to fully reindex (a 4h process).

See: Screenshot from Gyazo

@egraether
Copy link
Contributor

I see, we could remove this message box. But you still need to refresh those files that couldn't find a header, to get rid of the errors. How do you do that?

@TTimo
Copy link
Contributor Author

TTimo commented Oct 24, 2017

Well there's only 18 files out of 4k that had a fatal error .. so I guess the 'refresh' in Sourcetrail would be retrying those?

@egraether
Copy link
Contributor

We currently don't have an option to refresh only files with errors (incomplete files), but it would make sense to add this option. I opened #496 for that. Until that is implemented, we keep the force refresh on settings change.

@egraether egraether self-assigned this Nov 29, 2017
@egraether
Copy link
Contributor

Implemented with 2017.4.83

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants