Make it easier to select the entire trace

Open
#623 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
frontend

Research direction

The issue names no files or tests; start by locating the frontend interaction that handles tapping a trace segment and selecting or deleting a shape. Compare the current point-creation and whole-trace deletion behavior, then verify that the chosen interaction selects the entire trace without requiring point-by-point deletion.

Written by the indexing model from the issue text.

Description

front-end needs ui/ux design
Description

After removing long-press to place points, tapping on a line or segment now always creates a new point. The reason you may want to select the entire shape is to delete and start again, which we assume is less common.

Currently too delete a shape, users must either:

  • Manually select and delete each individual point
  • Or tap a segment, it turns dark blue to show the selected state (while also creating a new point), and then delete the entire line. Given they are going to delete the entire line the additional point likely won't be a big issue.

Checklist
  • Does it need UI/UX design?
    • Yes. Describe the UI/UX requirements or attach a Figma link in the "Design" section.
    • No
  • Does it need API design?
    • Yes. Specify the endpoints, methods, or data structures needed.
    • No
  • Does it need design around state flow?
    • Yes. Outline the state flow requirements.
    • No
  • Does it need a test plan?
    • Yes. Add the test plan as a comment in this task or attach the document.
    • No

User Stories
  • As a [user type],
    I want [functionality],
    so that [benefit].

Design
  • Figma: [Insert URL]
  • Design Docs: [Insert URL]

Dependencies

Additional Notes

Related Issues
Dominant language
TypeScript
Stars
38
Forks
24
PR merge metrics
No merged PRs in 30d

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

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.

More from getodk/web-forms

All issues in getodk/web-forms

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.