hub: freeze updates with incoming syntax errors?
Open
Nobody has claimed this yet.
enhancement
quarto-hub
- Dominant language
- Rust
- Stars
- 255
- Forks
- 17
- Avg merge
- 6h 20m
- Merged PRs (30d)
- 109
Description
Could we hold back automerge changes coming to the editor and preview window if they cause syntax errors? We could set a (eg) 3s timeout under the presumption that the incoming changes will soon include a fix for the syntax error.
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
Start by tracing the hub's automerge update path and how incoming changes reach the editor and preview window. Define how syntax errors and the proposed 3-second hold should be detected and scoped; done means invalid intermediate updates are withheld while later fixes can pass through.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100