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

Variable defaults and choice lists

Open
  • Is something wrong?
#59 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
csharp, sqlite
Domain
backend-api-design, developer-experience

Research direction

Start with ROADMAP.md’s market research entry dated 2026-10-10 and review issue #13 for the rendering contract. Decide and document the metadata key and shape, integration points, precedence, and versioning; then give this issue a milestone and checklist. Done when the dated decision and milestone checklist are in place.

Written by the indexing model from the issue text.

Description

enhancement later

Give a {{variable}} a default value or a short list of choices, so filling a prompt in is a pick instead of typing.

ROADMAP.md (market research, 2026-10-10) already decided the shape: defaults and choice lists live in an optional metadata key, not inside {{…}}. A body holding {{name|x}} renders as plain text in 1.0, and render must keep printing it (#13 pins that).

What has to be settled before this gets a milestone

  • The key. Its name and shape in the frontmatter. The frontmatter reader is hand-written with no YAML dependency, so the shape has to stay simple, such as one line per variable.
  • Where it shows. The Render tab, Quick insert (#24), workflows' shared variables, prompuff render and MCP prompt arguments.
  • Order of precedence. A remembered value, then the default, then the token left in place, as today.
  • Versions. Whether changing a default is a content change (a new version) or metadata.
  • Contracts. A prompt without the key renders exactly as in 1.0, and a fixture records the key once it ships.

Done when

  • The settled answers are a dated decision in ROADMAP.md, and this issue gets a milestone with its own checklist.
Dominant language
C#
Stars
0
Forks
1
Avg merge
1h 21m
Merged PRs (30d)
22

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 hazeliscoding/prompuff

All issues in hazeliscoding/prompuff

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.