# New Go library: Queryfy / Request For Comments

**URL:** <https://forum.golangbridge.org/t/new-go-library-queryfy-request-for-comments/39019>\
**Category:** Code Review\
**Created:** [June 14, 2025, 12:16am UTC](https://forum.golangbridge.org/t/new-go-library-queryfy-request-for-comments/39019 "2025-06-14T00:16:37Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![haitch](https://forum.golangbridge.org/letter_avatar_proxy/v4/letter/h/d26b3c/32.png) [@haitch](https://forum.golangbridge.org/u/haitch)\
**Post date:** [June 14, 2025, 12:16am UTC](https://forum.golangbridge.org/t/new-go-library-queryfy-request-for-comments/39019/1 "2025-06-14T00:16:37Z")

</div>

Hello community, it’s my first time here and I’m learning the ropes.

I’m developing Queryfy, a library for validating and querying `map[string]interface{}` data with compile-time safety.

**The problem:** Working with dynamic JSON in Go often means choosing between multiple tools (validator for validation, gjson for queries, mapstructure for conversion) or writing endless type assertions.

**My solution:** A unified API with type-safe builders that gives you IDE autocomplete and compile-time checking:

```go
schema := builders.Object().
    Field("email", builders.String().Email().Required()).
    Field("items", builders.Array().Of(itemSchema))

// Validate, query, and transform with one coherent API
err := qf.Validate(data, schema)
value, _ := qf.Query(data, "items[0].price")

```

Zero dependencies, clear error messages with paths, supports both strict and loose validation modes.

**My question:** This is my first significant OSS project. v0.1.0 is ready and tested, but I’m unsure about:

- How to handle contributions without getting overwhelmed
- Setting up governance/decision making
- Balancing feature requests with maintaining simplicity

Would love advice from maintainers who’ve successfully grown projects. How do you manage the human side of open source?

GitHub:

> **[GitHub - ha1tch/queryfy](https://github.com/ha1tch/queryfy#readme)**
>
> Contribute to ha1tch/queryfy development by creating an account on GitHub.

Work is ongoing in the /docs subdirectory

Code examples:

> **[queryfy/examples at main · ha1tch/queryfy](https://github.com/ha1tch/queryfy/tree/main/examples)**
>
> Contribute to ha1tch/queryfy development by creating an account on GitHub.
