Skip to content

:edn :coerce option must have explicit value#189

Merged
borkdude merged 1 commit into
mainfrom
lread/no-implicit-on-edn
Jun 26, 2026
Merged

:edn :coerce option must have explicit value#189
borkdude merged 1 commit into
mainfrom
lread/no-implicit-on-edn

Conversation

@lread

@lread lread commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

Coercing to implicit true for --foo and implicit false for --no-foo for :edn coercions was confusing for CLI usability.

--foo on an :edn option now generates a missing value error --no-foo on an :edn option now generates a cannot negate error.

Also added a brief section explaining :edn coercion to README. It wasn't previously covered.

Closes #174

Coercing to implicit `true` for `--foo` and implicit `false` for
`--no-foo` for `:edn` coercions was confusing for CLI usability.

`--foo` on an `:edn` option now generates a missing value error
`--no-foo` on an `:edn` option now generates a cannot negate error.

Also added a brief section explaining `:edn` coercion to README.
It wasn't previously covered.

Closes #174
@borkdude borkdude merged commit 4fd7504 into main Jun 26, 2026
26 checks passed
@borkdude

Copy link
Copy Markdown
Contributor

Thanks!

@borkdude borkdude deleted the lread/no-implicit-on-edn branch June 26, 2026 14:00
lread added a commit that referenced this pull request Jun 26, 2026
* main:
  `:edn` `:coerce` option must have explicit value (#189)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Should boolean flags coerce to :edn?

2 participants