You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Back at a time, the drivers were extracted from the db (this) repo to allow separate development of them.
Although it helped to cleanup lot of things, follow best practices per driver, better separation, etc., it makes some things harder during DB build and polyglot testing.
Let's take the golden middle way, and bring back the drivers as git submodules. That allows the flexibility and freedom for driver developers as mentioned above while the DB build pipeline and polyglot testing can be simplified.
Also, we could involve other drivers as we want, like the Go driver or the Typescript one.
Bring the Ruby driver back
Bring the Python driver back
Bring the JavaScript driver back
Food for thought:
Should we involve the Go driver?
Should we involve the Java driver?
Generally, what drivers should be involved in polyglot testing?
The text was updated successfully, but these errors were encountered:
Description
Back at a time, the drivers were extracted from the db (this) repo to allow separate development of them.
Although it helped to cleanup lot of things, follow best practices per driver, better separation, etc., it makes some things harder during DB build and polyglot testing.
Let's take the golden middle way, and bring back the drivers as git submodules. That allows the flexibility and freedom for driver developers as mentioned above while the DB build pipeline and polyglot testing can be simplified.
Also, we could involve other drivers as we want, like the Go driver or the Typescript one.
Food for thought:
The text was updated successfully, but these errors were encountered: