agentleFS
getprobogetprobo/probo/.cursor/rules/go-enum-array-valuer.mdc

probo / rules

Cursor rule1.5k starsChanged 20 days agoMITView on GitHub

Encode enum slices for PostgreSQL with driver.Valuer

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 2 mentionsOct 2026: 0 mentionsNov 2026: 48 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the getprobo/probo repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about getprobo/probo

The biggest 5 of 56 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 56

Talked about on GitHub, Hacker News and Bluesky (56 times).

On GitHub · 50

45 more on GitHub

The file

We split this go-enum-array-valuer.mdc into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Do not loop the values into []string at the call site.

    line 13

≈ “Common” is an estimate: at least 1 in 5 of the 6,809 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
go-enum-array-valuer.mdc
---
description: Encode enum slices for PostgreSQL with driver.Valuer
globs: "pkg/coredata/**/*.go"
alwaysApply: false
---

# Enum array arguments

pgx has no encode plan for a slice of a named string enum (`[]Status`) into an unregistered Postgres enum array. Passing that slice fails before the query runs.

Implement `database/sql/driver.Valuer` on a named slice type. `Value` returns the Postgres array literal via `%q`. Enum labels are plain ASCII tokens, so that matches what PostgreSQL parses. Keep `Scan` and `Value` off the singular enum; a single value encodes through `MarshalText`.

Do not loop the values into `[]string` at the call site.

Name the slice the plural of the enum when that name is free (`DocumentVersionSignatureStates`). When a plural helper already uses it (`Statuses()`, `States()`, `Types()`, or a longer name such as `AccessReviewCampaignStatuses()`), append `Values` to the enum type (`StatusValues`).

```go
// GOOD
type StatusValues []Status

var (
	_ driver.Valuer = StatusValues(nil)
)

func (values StatusValues) Value() (driver.Value, error) {
	if len(values) == 0 {
		return nil, nil
	}

	var result strings.Builder
	result.WriteString("{")

	for i, value := range values {
		if i > 0 {
			result.WriteString(",")
		}

		fmt.Fprintf(&result, "%q", value.String())
	}

	result.WriteString("}")

	return result.String(), nil
}

"statuses": StatusValues{StatusRejected, StatusRevoked},

// BAD — no encode plan for []Status
"statuses": []Status{StatusRejected, StatusRevoked},

// BAD — converts to []string instead of implementing driver.Valuer
encoded := make([]string, len(values))
for i, value := range values {
	encoded[i] = value.String()
}
```

An empty slice returns `nil`, so `WHEN @statuses::status[] IS NOT NULL` leaves the filter off. The SQL still casts the parameter: `status = ANY(@statuses::status[])`.

See [`contrib/claude/coredata.md`](../../contrib/claude/coredata.md) (Enum arrays).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.