hub: Replay for Quarto project changes
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 255
- Forks
- 17
- Avg merge
- 6h 20m
- Merged PRs (30d)
- 109
Description
Another useful thing would be a way for this mode to work on changes to the index document (Carlos edits: that is, the index document controls which files exist in the project itself). There, the UI gets a bit more complicated. Users never see the "content" of the index automerge document and don't know the representation, and so it's not trivial to show the equivalent of the editor and preview. The main thing we want to allow is for people to undelete files, but there are more complicated scenarios, like the fact that someone might have deleted a file from the project, then recreated a new file with the same name (but different automerge id)
Originally posted by @cscheid in https://github.com/quarto-dev/q2/issues/46#issuecomment-4068226385
Contributor guide
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
Begin by reading issue #46 and tracing the existing replay mode and index-document handling. The payload names no repository files or tests; done should cover a UI for index-document changes, including undeleting files and distinguishing a recreated file with the same name but a different Automerge id.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100