What happened?
When opening files from this repo (solutions secret for students)
the progress bar is quite inconsistent. It will either say "up to line 1", "up to line x", where x is the line before #doc or not be present, even when goals after line 1/x are already shown.
How can we reproduce this issue?
Example:
- Open any worksheet from the linked repo
- Observe the inconsistent behaviour
What was supposed to happen?
The progress bar should reflect the checking progress. Same for the progress marker.
Additional Information
The reason I've marked this as a spike is because I'm not sure it has a reasonable resolution: It could very well be that the LSP indeed only communicates this information with the given granularity.
When investigating this, pay attention to the proof bars as well.
Outcomes of this spike are answers to the following
- Is the problem indeed the LSP information not being granular enough, or is there another bug?
(#verso > Fine grained file progress suggests that the information should be available somewhere)
- If yes, Could we get more finegrained progress from the LSP?
- If yes, describe the technical steps needed to improve this
- If no, describe the best mitigation possible to retain this information
- Design proposal or prototype for the progress reporting behaviour.
Also possibly related to impermeable/waterproof-editor#77
What happened?
When opening files from this repo (solutions secret for students)
the progress bar is quite inconsistent. It will either say "up to line 1", "up to line x", where x is the line before
#docor not be present, even when goals after line 1/x are already shown.How can we reproduce this issue?
Example:
What was supposed to happen?
The progress bar should reflect the checking progress. Same for the progress marker.
Additional Information
The reason I've marked this as a spike is because I'm not sure it has a reasonable resolution: It could very well be that the LSP indeed only communicates this information with the given granularity.
When investigating this, pay attention to the proof bars as well.
Outcomes of this spike are answers to the following
(#verso > Fine grained file progress suggests that the information should be available somewhere)
Also possibly related to impermeable/waterproof-editor#77