How typedgrammar/typed-japanese works
• DSL Core – This represents the central type-level engine. It includes the core grammatical rules and type definitions (located in src/ files such as index.d.ts and the various *-types.d.ts files).
• Verb System – Covers Godan, Ichidan, and Irregular verbs. Indicate components for conjugation forms (dictionary, ます形, て形, etc.) and the underlying transformation logic (using TypeScript’s conditional and template literal types).
• Adjective System – Include components for I-Adjectives and Na-Adjectives, together with the conjugation transformations.
• Other Grammar Elements – Such as noun types, adverbs, phrases, and particles. (Note these could be grouped or placed side-by-side if needed.)
• Examples/Demonstration Module – Represented as a distinct area (src/examples) which shows example usage of the DSL. This demonstrates how developers can “write” Japanese sentences and leverage the type-checker for correctness.
• Configuration and Build Infrastructure – Although not part of the DSL per se, include components for the development environment:
• Project Configuration Files (tsconfig.json, eslint.config.js, .eslintrc, package.json, pnpm-lock.yaml)
• CI/CD Pipeline (GitHub workflows from the .github/workflows/ci.yml file)
Technology and Frameworks
• That the entire project leverages TypeScript’s type system (i.e., no runtime logic) and relies on Node.js and pnpm for dependency management and testing.
• Use of CI/CD workflows (GitHub actions) which are used to enforce quality via tests and linting.