tc39 / tc39/ecmarkup

Support automatically generating Unicode property lists

Open
#193 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
245
Forks
80
Avg merge
10h 46m
Merged PRs (30d)
2

Description

PRs like https://github.com/tc39/ecma262/pull/1939 and https://github.com/tc39/ecma262/pull/1896 could (and should) be done automatically as part of the tooling.

@mathiasbynens maintains a collection of npm modules which could be used for this. Note that these bump Unicode versions in minor releases, so for this use case we'd want to pin a minor version.

Contributor guide

Open the 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.

Research direction

Start by reviewing the linked ecma262 PRs and the Unicode-data npm module collection referenced in the issue. Determine where ecmarkup tooling should generate these property lists and how to pin a Unicode minor version. Done means equivalent changes can be produced automatically as part of the tooling.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.