feat: expose connector name

[beeequeue]

this pr exposes the name of the connector via the db instance, this is useful for libraries integrating with db0 that otherwise have to do workarounds to know what connectors are being used

Summary by CodeRabbit

• New Features
  • Added a read-only connector name property to database instances.
  • Database consumers can now identify which connector is being used.

[pi0]

Thanks!

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 71a16d65-7b14-4964-8545-c3a690871998

📥 Commits

Reviewing files that changed from the base of the PR and between d2a0e70 and 031426c.

📒 Files selected for processing (2)

• src/database.ts
• src/types.ts

---

📝 Walkthrough

Walkthrough

Database now exposes the connector name through a typed readonly property, backed by a getter on the object returned from createDatabase.

Changes

Database Connector Name

Layer / File(s)	Summary
Typed connector property src/types.ts, src/database.ts	Database declares readonly connector: ConnectorName, and createDatabase returns the connector name through a getter.

Estimated code review effort: 1 (Trivial) | ~5 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately and concisely reflects the main change: exposing the connector name on the db instance.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

ESLint install failed. For unrecoverable errors, disable the tool in CodeRabbit configuration.

---

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.}