tursodatabase / tursodatabase/libsql-client-ts
Support readonly connections
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 576
- Forks
- 69
- PR merge metrics
- No merged PRs in 30d
Description
https://github.com/tursodatabase/libsql-js/issues/24 asked for readonly support in the JS client.
That issue was marked as blocked on https://github.com/tursodatabase/libsql/issues/344.
https://github.com/tursodatabase/libsql/pull/347 was opened to address 344, then closed in favor of https://github.com/tursodatabase/libsql/commit/befd7357cc5b7aa6cd150f511649f90c8d2c0597.
expandConfig doesn't support a mode=ro option, so this library prevents its use.
I'm happy to contribute, review, QA, or help in any way I can.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in packages/libsql-core/src/config.ts at expandConfig, which currently does not support a mode=ro option. Check how connection configuration is passed through the TypeScript client, then verify that readonly connections can be configured without breaking existing options.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sqlite, typescript
- Domain
- database
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100