Prefill the engine diagnostics field on crash-report bug links
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
Research direction
Start in src/game/crashReport.ts at bugReportUrl, then read crashReport.test.ts and check how the existing version and what-happened query parameters are built. Prefill the diagnostics textarea with the engine diagnostics text while keeping the URL within its length budget. Update the test to verify the parameter, and confirm the Engine dropdown is not being prefilled.
Written by the indexing model from the issue text.
Description
Backlog row bug-form-crash-prefill-diagnostics. Deferred from the independent review of PR #1200 (the Engine dropdown and Engine diagnostics field on the bug report form).
The crash screen's bug link (bugReportUrl in src/game/crashReport.ts) prefills version and what-happened through query parameters. It could also prefill the form's diagnostics textarea with the engine diagnostics text, which names the engine and any fallback. Prefill the textarea, not the Engine dropdown: what-happened already proves textareas take a query-parameter value, and the diagnostics text makes the dropdown redundant for crash reports. Test in crashReport.test.ts. Not needed for 3.0; if dropped, nothing is lost, since the crash zip carries the crash details.
Also check the URL length budget before adding the text.
- Dominant language
- TypeScript
- Stars
- 6
- Forks
- 1
- Avg merge
- 9h 22m
- Merged PRs (30d)
- 179
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from maniator/verticopolis
-
Make npm environment-variable scripts work on Windows via cross-envPossibly taken @maniator claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
maniator/verticopolis#1303 · 1 comment · 1 reaction · 2 assignees ·
Maintainers usually reply within 1 day
-
bug P3
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
maniator/verticopolis#1249 ·
Maintainers usually reply within 1 day
-
bug P1
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
maniator/verticopolis#1162 ·
Maintainers usually reply within 1 day
-
engine-rs P3 review-deferral task wasm
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
maniator/verticopolis#1154 ·
Maintainers usually reply within 1 day
-
enhancement P3 wasm
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
maniator/verticopolis#1151 ·
Maintainers usually reply within 1 day
All issues in maniator/verticopolis
Similar issues
-
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
source-cooperative/docs.source.coop#41 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Nimblesite/SharpLsp#468 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
solidjs-community/solid-primitives#1082 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day