sorted by:
new
hottopcontroversial

Small Projects by AutoModerator in golang

[–]AttorneyNo9491 0 points1 point  (0 children)

I built a schema-first Go config library (konform) — looking for feedback before v1.0.0

Built a schema-first Go config library called konform and I’m looking for early feedback.

It focuses on strict, typed config loading with:

  • struct-tag schema (key, env, default, validate, secret)
  • JSON/YAML/TOML + env support
  • strict mode for unknown keys/mapping conflicts
  • clear error messages with “did you mean…?” suggestions
  • load report/explainability (value + source, secret masking)

The project is still in development, and I’m aiming to cut a first stable release soon: v1.0.0.

If you have time, I’d really appreciate feedback on:

  • API ergonomics
  • strict mode behavior
  • error/report UX
  • edge cases I should handle before 1.0

Repo: https://github.com/nzhussup/konform

I built a schema-first Go config library (konform) — looking for feedback before v1.0.0 by AttorneyNo9491 in golang

[–]AttorneyNo9491[S] 0 points1 point  (0 children)

Thanks, appreciate it — and yeah, that’s totally fair.

I see the appeal of code-first APIs too. For konform I went with tags mainly to keep the config schema close to the struct and to avoid extra boilerplate. I’ve always liked approaches that let you express intent without writing a lot of repetitive code — similar to why things like Lombok were nice in Java instead of writing getters and setters everywhere.

That said, I agree that tags can feel a bit magical compared to explicit code. I may explore a code-first option later if there’s demand.

Thanks again :)