refactor(postgrest-typegen): drop the unused postgres-meta options from the introspection

[spydon]

Stacked on #179.

Summary

The introspection SQL builders were ported from postgres-meta's managers together with every option those managers accept: limit, offset, idsFilter, nameFilter, tableIdentifierFilter, viewIdentifierFilter, columnNameFilter, tableIdFilter, the args filter of the functions query and the includeTableTypes/includeArrayTypes flags of the types query. introspect() sets exactly one of them, the schema filter. The builders are not exported from the package and nothing else in the repository passes the other options, so they were unreachable code that still had to be read around.

• Every builder now takes SchemaFilterProps, a required schemaFilter and nothing else. TYPES_SQL becomes a constant since it had no variable part left.
• The args block of FUNCTIONS_SQL, a nested ternary interpolating a string[] through Array#toString, goes away together with the file-wide lint suppression it needed.
• The rendered SQL loses all but one conditional filter line per builder, and with it most of the blank lines with trailing whitespace.
• introspect() no longer re-filters the schemas rows in JavaScript. The query already applies the same include and exclude filter; the only case where the two differed was a schema listed in both lists, which the JavaScript filter dropped from schemas while every other collection still contained it.
• introspect() passes the filter it already built to listRelationships instead of having it rebuilt from the options.
• The cartesian product in expandViewRelationships is a flatMap instead of the gist-linked map/reduce pair.

Verification

• bun run test with Docker: 133 pass, including the introspection integration tests and the view relationship expansions.
• SQL snapshots in sql.test.ts regenerated; the diff is the removed blank lines, the constant TYPES_SQL, and the schemas query's unconditional pg_ exclusion.
• check-types, format-and-lint and knip pass.

Generated output is unchanged for every option combination introspect() can produce, so the byte-parity constraint with postgres-meta holds.

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 2118ddd1-bbc1-4fad-bb3d-26774127cced

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}