-
Notifications
You must be signed in to change notification settings - Fork 155
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore (drivers): extract drivers to a separate package #1332
Conversation
b4deb74
to
13245fd
Compare
d2f8080
to
2ebe05b
Compare
362ed3a
to
2d1f8a3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great, nice work!
My only concern is with the extraction of some utilities, like the QualifiedTablename
class, parseTableNames
, and parseDate
, which end up being core to the client as well but they belong to the drivers package, despite them only being used in tests or not used at all in the whole of the driver package.
I wonder if, since they are so few as well, we might benefit from keeping them in the client and re-implementing thinner abstractions for the drivers only?
…erwise we get subtle type compatibility issues.
… the compiled dist/bin.js file because pnpm install would fail if dist/bin.js does not exist but in order to build dist/bin.js we first need to pnpm install.
…iles on Node >=v18.19.0
…bleName and parseTablenames to ts-client package
0fd9737
to
ee33c9e
Compare
No description provided.