leanprover / leanprover/vscode-lean4

RFC: Have 'restart file' button show how many files would be rebuilt

Open
#771 0 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

RFC
Dominant language
TypeScript
Stars
313
Forks
104
Avg merge
1h 56m
Merged PRs (30d)
1

Description

Proposal

Clicking 'restart file' may have an effect between rebuilding just a few dependencies that were recently changed, and rebuilding all of mathlib. It would be a UX improvement to display this information. See also #693 which would interact with this.

  • User Experience: Clarify how heavy the restart action would be.

  • Beneficiaries: All users of large projects.

  • Maintainability: Likely requires additional code paths.

Community Feedback

https://leanprover.zulipchat.com/#narrow/channel/270676-lean4/topic/Lake.20UX.20problems/near/586341063

Impact

Add 👍 to issues you consider important. If others benefit from the changes in this proposal being added, please ask them to add 👍 to it.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the proposal and the linked Zulip discussion about Lake UX problems, then compare the interaction with issue #693. No files, entry points, or tests are named, so the first step is to locate the restart-file action in the VS Code extension. Done means the button communicates how many files would be rebuilt without disrupting the existing restart behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
developer-experience, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.