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

templates: no conditional {{#if}} blocks and no localization

Open
#208 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 4 days

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
content

Research direction

Start by locating the template engine and the TemplateOverride model or entry point. Implement and verify conditional blocks first, including {{else}} and preserved escaping; then assess the locale dimension needed for per-locale overrides. Done means templates support the specified conditional behavior and localization requirements from the original spec.

Written by the indexing model from the issue text.

Description

area: product roadmap roadmap: later

Two related gaps in the template engine, both listed in the original spec (Setup, Team Management & Template System) and unbuilt:

  1. Localization — templates are English-only, with no locale selection or per-locale override.
  2. Conditional blocks — no {{#if}} support, so a template cannot vary on whether a value is present. Today that forces either two near-duplicate templates or a sentence that reads awkwardly when a field is empty.

Why it matters

Neither blocks launch. Conditionals are the one with day-to-day cost — every optional field in a template is currently a copy-paste fork.

Fix

Conditionals first (smaller, immediately useful): {{#if field}}...{{/if}} with an {{else}} arm, escaping preserved throughout. Localization after, keyed off TemplateOverride with an added locale dimension.

Dominant language
TypeScript
Stars
10
Forks
4
Avg merge
4d 2h
Merged PRs (30d)
7

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No 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.

More from CopilotKit/outpost

All issues in CopilotKit/outpost

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.