The selector assumes you are a builder, not a consumer
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 10
- Forks
- 8
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 2
Description
First of all, this tool is fantastic!
One observation, however, is that the tool comes from the perspective of the builder, not the consumer. Although this tool is essential for builders to create content that is tagged correctly with the right BCP-47 code, that use will potentially be dwarfed by consumers who will use it to select content in their language.
This impacts the following two aspects of the dialog, which are not relevant for consumers, but only builders:
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files or tests; start by locating the selector dialog and reviewing the two builder-focused aspects shown in the attached images. Done means agreeing on and implementing a consumer-oriented dialog that addresses those aspects, with behavior validated for both consumer and builder use.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, internationalization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100