Should alchemy adjust for the random ways spec authors write "empty"

Open
#23 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
go
Domain
cli

Research direction

The issue names no files, tests, or entry points. Start by tracing Alchemy's handling of spec values represented as [], empty, and "", then compare the current behavior for each form. Done means the intended behavior for these representations is covered and works consistently in released-version processing.

Written by the indexing model from the issue text.

Description

We have [], empty, "". Honestly, we should fix in spec, but it's harder for released versions.

Dominant language
Go
Stars
10
Forks
12
Avg merge
23h 54m
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

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 project-chip/alchemy

All issues in project-chip/alchemy

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.