leanprover / leanprover/vscode-lean4
Merge vscode-lean4-code-actions?
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 313
- Forks
- 104
- Avg merge
- 1h 56m
- Merged PRs (30d)
- 1
Description
Hi @Vtec234 @gebner !
I've published a new VSCode extension for code actions.
Mario suggested merging this extension into vscode-lean4 in the Zulip thread.
Pros:
- Users won't need to install two extensions.
Cons:
- Lower release speed: the PRs would need to go through the review process.
- Lower dev speed: I'll have to adjust to the code style, packages, testing framework, etc (or we could have lengthy discussions, but that would result in even lower speed).
Are there any missing pros / cons?
What do you think in general: should we merge?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked VSCode extension and the referenced Zulip thread, then read the discussion in this issue. The issue is complete only after the maintainers decide whether to merge the extension and define the integration scope; no files or tests are identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100