getodk / getodk/web-forms

Engine module structure: consider grouping by "node type" or other client-facing concept

Open
#282 0 comments 1 reaction 0 assignees View on GitHub
Dominant language
TypeScript
Stars
38
Forks
22
PR merge metrics
No merged PRs in 30d

Description

As suggested in [this comment](https://github.com/getodk/web-forms/pull/277#discussion_r1920533235) on #277.

I'm opening this as a stub issue for now so I can reference it in response to that comment. We can fill out details as appropriate.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reading the linked discussion on pull request #277 and inspecting the current engine module structure. No files or tests are named, so first determine which client-facing concepts the modules represent and agree on the intended grouping. Done means the structure and scope are clearly defined for implementation.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.