Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add missing German and English verb synonyms to the parser

Open Beginner friendly
  • Is something wrong?
#27 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
86/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
backend

Research direction

Read packages/engine/src/messages/de.ts and en.ts for vocab.verbs and vocab.directions, then inspect the parser cases in packages/engine/test/parser.test.ts. Add the listed German and English synonyms with one parsing test per entry, and verify existing parser tests and npm run check:packs pass.

Written by the indexing model from the issue text.

Description

area: engine good first issue priority: low type: feature

Context

The parser vocabulary lives in two tables: packages/engine/src/messages/de.ts and en.ts (vocab.verbs and vocab.directions). v0.1 added steig and steige for go after the noir playtests, but some common phrasings are still rejected as unknown verbs: German steigen and verlass, verlasse; English tell (the table has ask for talk) and exit.

Scope

  • Add:
    • German: steigen (go, like steig in "steig hinauf"); verlass, verlasse (the out direction).
    • English: tell (talk); exit (the out direction, like leave).
  • Before adding any further candidate, check with a test that it is really rejected today (for example "unterhalte dich mit" and "chat with" already work).
  • One parser test per new entry, in the style of packages/engine/test/parser.test.ts.
  • No pack format change; pack verbs still win over core phrases.

Acceptance criteria

  • Every added synonym has a test that parses it to the expected canonical command.
  • Existing parser tests pass unchanged, including "lets pack verbs override core phrases, even the internal unlock shortcut".
  • npm run check:packs passes.

References

  • packages/engine/src/messages/de.ts
  • packages/engine/src/messages/en.ts
  • packages/engine/test/parser.test.ts
  • CONTRIBUTING.md (Development setup)
Dominant language
TypeScript
Stars
0
Forks
0
Avg merge
28m
Merged PRs (30d)
2

Getting set up

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 nullthrone/lexvm

All issues in nullthrone/lexvm

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.