refactor: generic database config parsing

[0237h]

Summary

• Replace hardcoded database field parsing in dbsConfig.ts with a generic loop that maps any YAML key to ${key}Databases
• New database types can be added to dbs-config.yaml without modifying the Zod schema — only the ParsedDbsConfig interface needs a new property
• Rename nftDatabases → nftsDatabases, dexDatabases → dexesDatabases, contractDatabases → contractsDatabases to align with YAML key names (nfts, dexes, contracts)
• Add Polymarket entry to dbs-config.yaml.example
• Add unit tests for loadDbsConfig

Refs: #461

---

🤖 Generated with Claude Code

[Copilot]

Pull request overview

This PR refactors database YAML config parsing to be generic (mapping arbitrary YAML keys to ${key}Databases), updates config property names to match YAML keys (nfts/dexes/contracts), and wires the new names through route code.

Changes:

• Refactor loadDbsConfig to generically map network-level YAML keys into typed ${key}Databases maps and return an always-initialized config object.
• Rename config accessors across routes (dexDatabases→dexesDatabases, nftDatabases→nftsDatabases, contractDatabases→contractsDatabases).
• Add loadDbsConfig unit tests and extend the example YAML (including a Polymarket stanza).

Reviewed changes

Copilot reviewed 29 out of 29 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
src/config/dbsConfig.ts	Implements generic YAML-to-{key}Databases parsing and updates parsed config typing.
src/config/dbsConfig.spec.ts	Adds unit tests for loadDbsConfig.
src/config.ts	Spreads parsed DB maps into runtime config and updates network derivation to renamed maps.
src/clickhouse/client.ts	Updates cluster lookup to use renamed maps and includes new maps.
src/supported-routes.ts	Updates DB category map to use renamed config properties.
src/supported-routes.spec.ts	Updates tests to use renamed config properties.
src/banner.ts	Updates logging to use renamed config properties.
src/routes/networks.ts	Updates dex DB reference to renamed config property.
src/routes/health.ts	Updates DB fallback selection to renamed config properties.
src/routes/transfers/svm.ts	Updates dex DB reference to renamed config property.
src/routes/swaps/{evm,svm,tvm}.ts	Updates dex DB reference to renamed config property.
src/routes/pools/{evm,svm,tvm}.ts	Updates dex DB reference to renamed config property.
src/routes/ohlcv/{evm,svm,tvm}.ts	Updates dex DB reference to renamed config property.
src/routes/dexes/{evm,svm,tvm}.ts	Updates dex DB reference to renamed config property.
src/routes/nft/*.ts	Updates NFT/contracts DB references to renamed config properties.
dbs-config.yaml.example	Updates documentation and adds a Polymarket example entry.

Comments suppressed due to low confidence (1)

src/config.ts:364

• config.networks is built solely from evmNetworks, svmNetworks, and tvmNetworks, which in turn are derived only from balances/transfers/nfts/dexes/contracts maps and strict type checks (=== 'evm'|'svm'|'tvm'). Any network present only in newly added maps (e.g. polymarketDatabases / scraperDatabases) or with a nonstandard type will never appear in config.networks, which can break endpoints/schemas that rely on config.networks as the canonical network list. If the intent is to support these as real networks, consider including the new maps (and/or a new network-type bucket) in the network list derivation.

    .transform((data) => ({
        ...data,
        evmNetworks: Object.keys({
            ...data.balancesDatabases,
            ...data.transfersDatabases,
            ...data.nftsDatabases,
            ...data.dexesDatabases,
            ...data.contractsDatabases,
        })
            .filter((networkId) => {
                return (
                    {
                        ...data.balancesDatabases,
                        ...data.transfersDatabases,
                        ...data.nftsDatabases,
                        ...data.dexesDatabases,
                        ...data.contractsDatabases,
                    }[networkId]?.type === 'evm'
                );
            })
            .sort(),
        svmNetworks: Object.keys({
            ...data.balancesDatabases,
            ...data.transfersDatabases,
            ...data.nftsDatabases,
            ...data.dexesDatabases,
            ...data.contractsDatabases,
        })
            .filter((networkId) => {
                return (
                    {
                        ...data.balancesDatabases,
                        ...data.transfersDatabases,
                        ...data.nftsDatabases,
                        ...data.dexesDatabases,
                        ...data.contractsDatabases,
                    }[networkId]?.type === 'svm'
                );
            })
            .sort(),
        tvmNetworks: Object.keys({
            ...data.transfersDatabases,
            ...data.dexesDatabases,
        })
            .filter((networkId) => {
                return (
                    {
                        ...data.transfersDatabases,
                        ...data.dexesDatabases,
                    }[networkId]?.type === 'tvm'
                );
            })
            .sort(),
    }))
    .transform((data) => ({
        ...data,
        networks: [...data.evmNetworks, ...data.svmNetworks, ...data.tvmNetworks],
    }))

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.